I wasn't fibbing; it is disingenuous to lie in support of a cause. I did genuinely encounter this issue. But with what you've said, I'll accept that it wasn't t

I wasn't fibbing; it is disingenuous to lie in support of a cause. I did genuinely encounter this issue. But with what you've said, I'll accept that it wasn't to blame upon snap. While the package wasn't named "sshd", that's an abbreviated way to refer to the ssh daemon. The package name varies between distros, but the config file and executable are known as "sshd". I was installing the ssh daemon package by whatever name the Debian/Ubuntu maintainers christened it. Something else must've broken it, then.