Yes absolutely. I must’ve misinterpreted what you said. What did you mean by “not visible anymore over the network.”
I’ve only used dropbear on openwrt systems, but I’m pretty sure it doesn’t use the '/etc/ssh/sshd_configfile. The alpine wiki says the config file is at/etc/conf.d/dropbear`.
That bit about the pi not being visible in the network after reboot makes me wonder if this is more of a networking issue rather than an ssh one.
The pi zero is WiFi-only, right? Can you confirm that it’s getting on the WiFi network successfully? If so, maybe it’s getting a different IP than it initially did via DHCP.
I pretty much stick to straight bash and core utils, so it’s not much of a burden. Plus on the Linux side, I mostly stay with Debian and its derivatives, which limits some of the work.
But really I don’t consider every feature of my dot files to be a finished product. The core stuff is reliable, but if I catch a problem with anything more esoteric or if I see some functionality that looks interesting, it’s a brain teaser I get to tackle.
I do a git repo for my dot files with an installer that configures it based on whether I’m using Linux, macOS, or FreeBSD; a server or desktop; and whether I’m in bash or zsh. It also includes a bunch of functions and aliases that I find useful. It’s not always pretty because I also use it as a practical place to try new shell script bits when I have time. I’m hoping to change some things around soon thanks to some ideas from Dave Eddy’s bash course at ysap.sh.
Way to go!