On Wed, 12 Dec 2018 10:15:58 +0100, A. Dumas wrote:

> That's fine, but sometimes, in some situations, you will run into
> trouble because user 'pi' is hardwired into stuff. Like in raspi-config,
> I think; or at least it was. So that might be a reason to switch back to
> the standard user. Two solutions for your workflow:
>
I haven't run into anything like that since I've had the RPi.

I may well have used sudoers but, since $EDIT points to microEmacs
globally, thats certainly what it will use. I looked at nano once and
decided it was so limited compared with microEmacs and vim that it wasn't
worth bothering with.

> Or, you know, keep it if you're only using ipv4 on NAT and/or behind a
> firewall and you don't do stuff that might get you a virus.
>
That's where it is: inside my firewall on a wired IPV4 LAN.

I don't use a GUI on it because I'm old school enough (miniMop, George 3,
VME/B, FLEX, MS-DOS, vos, mvs, OS/9, Guardian, OS/400, several Unices and
Linux in about that sequence) that I still do most development from the
command line because I hate being slowed down by the continual switching
between mouse and keyboard that most GUIs need.

> For The Nat Phil: it isn't about secret stuff that might get stolen but
> your machine getting hijacked by botnets for spam or ddossing, which
> will make your isp block you from the internet.
>
Agreed.

As another, slightly paranoid, precaution I have my ADSL router locked up
really tightly. Its configured to reject all attempts to connect through
it from the outside. In fact it can't be seen at all from outside: this
is checked periodically with Gibson Lab's ShieldsUp tool.

What about incoming mail? I use getmail to collect that from my ISP's
smarthost, a cronjob checks for incoming every 10 minutes.


--
Martin    | martin at
Gregorie  | gregorie dot org

--- SoupGate-Win32 v1.05