3 ms·
Why is this "modern replacement for OpenSSH" when people use ssh specifically because it's so simple and doesn't have webui? There have been many ssh webuis in
by akerro 6y ago
Why is this "modern replacement for OpenSSH" when people use ssh specifically because it's so simple and doesn't have webui? There have been many ssh webuis in the last decade, none of them were "replacements" of ssh, just wrappers for people scared of terminals. What exactly does it do that 20 other ssh wrappers (or even portainer for containers) don't?
- chucky_z 6y agoIt's really slick, and provides a client/server architecture with a bunch of extra security on-top. It generates 1:1 certificates between the api layer and the clients, using a full auth service. I deployed it at a previous position and stopped SSH across all hosts entirely, and just used this. It rotated all it's own certificates every 4 hours, and each SSH connection used a unique certificate. I never had any issues with it, and I had the web UI straight up exposed to the internet. It enforces TOTP and user management with the OSS stuff is pretty trivial. It also did something really cool, which is that I had multiple bastions federated together through a single API, instead of having singular multiple bastions. This meant no configuration to access hosts between prod/stage/test, all a single entry point, it was awesome. I don't use it today in my current position for a number of reasons, but if I were to go back to a smaller company and had the choice, I would deploy it with no hesitation.