Re:Why aren’t we using SSH for everything? (2015)
by mrmondo on Saturday February 04, 2017 @09:10AM
(#13567007)
While I agree with all the pros of SSH, the only issue for me is that you're spawning a remote shell which if not properly maintained / configure _could_ be a security risk, not because of ssh / key based authentication which are both great - but because you're one layer closer to the underlying OS - again which is fine if it's configured and secured properly but from what I've seen it's becoming more and more prevent for people to deploy servers / instances without truly understanding platform operations to a level where they choose a sensible OS distribution, keep SELinux enabled, run services in cgroups, automate patching etc... etc... and I think that's fine from the devaluing of operational experience and the whole replace one (modern) ops engineer with 5 devs mentality without considering that it may be more efficient to hire people and create roles based on their skill set and passion where they'll thrive best.
[ Parent
| on HN ]
Re:Why aren’t we using SSH for everything? (2015)
by 3onyc on Saturday February 04, 2017 @09:37AM
(#13567091)
This uses golang.org/x/crypto/ssh which doesn't spawn a shell, but handles the SSH connection like you would any other network connection. And the same could and should be done for the other mentioned examples as well.
Re:Why aren’t we using SSH for everything? (2015)
by ycmbntrthrwaway on Saturday February 04, 2017 @09:46AM
(#13567116)
Using sshd for SSH services is like using inetd for TCP services.
Re:Why aren’t we using SSH for everything? (2015)
by throwawayish on Saturday February 04, 2017 @10:02AM
(#13567174)
SSH != remote shell -- pretty much one of the main points of this article.