4 ms·
replacing openssh with something you've written yourself seems like reinventing the wheel, just because you can. the sheer number of person-hours at developer
by walrus01 11y ago
replacing openssh with something you've written yourself seems like reinventing the wheel, just because you can.
the sheer number of person-hours at developer salary rates in north america would probably amount to at least a few million dollars.
- tptacek 11y agoExcept that OpenSSH is a very large, complicated, and featureful piece of C code that most servers need only a tiny portion of.
- belak 11y agoYou'd be surprised. Go actually has a supported SSH library which is a fairly decent protocol-level implementation. To actually get a "shell server" you would need to implement handling of SSH sessions (as described in the RFCs) but all the low level stuff is taken care of. EDIT: As an example, the gogs project has implemented a small ssh server so people running it don't need to hook into OpenSSH, which relies on specific versions of OpenSSH to be performant. See https://github.com/gogits/gogs/blob/master/modules/ssh/ssh.go https://github.com/gogits/gogs/blob/master/modules/ssh/ssh.g...