3 ms·
I use normal opensshd for this. No reason to support two ssh daemons when you can do it with one. The difference in size on your init image is minimal and you
by jethro_tell 3y ago
I use normal opensshd for this.
No reason to support two ssh daemons when you can do it with one.
The difference in size on your init image is minimal and you probably aren't even trying to optimize for space there.
If you don't know the size of your rd off the top of your head then it almost certainly doesn't matter.
- bretthoerner 3y agoAll fair, I guess I just landed on mkinitcpio-tinyssh first and it was my introduction to the idea, and only took a few seconds to setup. I'll switch to openssh if I ever have issues, but this has been working fine for many years, so I'm no rush.
- jethro_tell 3y agoMakes sense. Probably more work to go off the beaten path then to maintain two configs
- streb-lo 3y agoProbably not more popular because (for reasons I do not know) the mkinitcpio hooks Arch Linux provides are only for tinyssh and dropbear: https://wiki.archlinux.org/title/dm-crypt/Specialties#Remote_unlocking_of_root_(or_other)_partition https://wiki.archlinux.org/title/dm-crypt/Specialties#Remote...