The Grumpy Editor's guide to SSH servers
Posted Jun 21, 2006 20:26 UTC (Wed) by kirkengaard
Parent article: The Grumpy Editor's guide to SSH servers
This seems to be the case with many de facto standard codebases. Like monolithic shade trees, it is hard for anything to grow in their shadow; most things that try to fill the same niche wind up compared to the 'big tree', just as dropbear and lsh do here. This is, to some extent, a self-reinforcing issue, and it can have good results, as you pointed out. A monoculture built around fanatic security-consciousness is perhaps more stable than some others. Big trees of this sort eat up a large share of their noosphere 'ground', and take up a very large share of the developer attention 'light'. Consider that dropbear lives by filling an available niche in the SSH market. There is ground and light for their particular choices. Lsh seems to be suffering the "Me, too!" that the GNU reimplementation tendencies can drive people to. The developer's itch is not common enough; OpenSSH is not enough of a pain to drive quality and masses to a GNU reimplementation.
I don't mean to sound like I'm complaining about the quality of the competition like it's OpenSSH's fault. This is a group choice in large part. It could be worse; at least this dominant player is nominally on the Open side of the fence, even if prickly at times. I've always thought of the logo as a caveat. ;)
to post comments)