A Geek Goes Flying

Local DNS setting in PiHole Local DNS I have a CNAME on my main domain that resolves to a DDNS name that’s kept updated from my home network. (Before:  https://freedns.afraid.org/  now whatever the MikroTik supplies, with the FreeDNS name  as a backup - two is one, one is none). It worked fine for years but now it’s not resolving properly from inside the LAN. I’'ll troubleshoot that one day but for now, the expedient fix was just to map that host to the internal IP address on the PiHole (6.3 core version, 6.4 web), since the MikroTik is using that as its DNS source. That was easy. Tahoe SSH authentication issues But now... Why can’t I login to any of my boxes (even remote) using SSH? Attempts hang at:  debug1: Next authentication method: publickey AI tells me it’s likely an issue with macOS Tahoe’s launchd sockets¹?). I was able to connect to the router via SSH and a password (bypassing the public key exchange) using either one of these: % SSH_AUTH_SOCK=/dev/null ssh...

I was today years old when I learned that SSH wasn’t a thing until around the summer of 1995 ! (I first learned about it the summer of 1997, when I was at HIP and all the l33t haxxors were sniffing my telnet sessions.) Wonder if I can run SSHeven on my PowerBook...  I’m reasonably sure I used F-Secure’s SSH client on my System 7.5.5 Mac back in the day? Though it could have been Nifty Telnet or ...  And it was definitely Tera Term and later Putty on my Windows machines, before I went back to Mac circa OS X Panther on an iBook G3 (IIRC a 600 MHz model ?). (As a native UNIX , of course, OS X had SSH built in, accessible from any terminal window.) And when setting up a new Solaris 8 machine, our first stop would always be sunfreeware.net to download OpenSSL and OpenSSH. macOS shell in cool-retro-term