I love Guacamole, but the authentication options leave a lot to be desired, in the sense that it defaults to saving passwords for all connections defined, which is nice for usability and, say, having predefined accounts for monitoring but a security nightmare for other purposes.
I wish the default were to prompt users to _always_ authenticate against the target systems, and store no passwords whatsoever.
The install process is still very non trivial, to say the least. The usage expirience is very smooth, though, anazingly for RDP contained in a browser. Some browser addon to supplement the Keyboard shortcuts might be required if I want to use it as a regular phyisical console to a cloud desktop. All in all, pretty cool software!
Would it be possible to use Guacamole in a setup with a server and a client, if neither the server or the client has an externally visible IP, and their firewalls cannot be configured?
Alternatively, are there other solutions which make it "easy" to enable SSH access to the server in such a scenario?
They are exploring making it work over webrtc which would support such a use case (although you'd still need a signaling server to setup the initial connection)
I've used guacamole many times and can only say good things about it. It's much easier to give a client web based access to their server than explaining how to use remote access.
Have set this up many times for less tech-savy friends. What I actually did was have them install docker-compose and provided them with a compose script to build up the latest version. I wouldn't use it myself though, I don't think I'd sleep well at night having a single factor auth webserver with access to my entire network.
The project graduated out of incubator status on the 15 Nov... I don't see a formal announcement about it anywhere, and that isn't really apparent from the page (other than the URL change). Not sure if that is why it was posted or not, but that seems to be what is different from the last time it was posted.
I think they mean 'agentless' rather than 'clientless'. You don't need to install anything special on the remote machines, just enable standard remote access protocol (ssh, rdp, vnc, etc)
Also related. Thinlinc is free for 5 users and has a web and client access. Includes drag/drop file access, vnc accelerated video, sound, video resizing, etc.
I wish the default were to prompt users to _always_ authenticate against the target systems, and store no passwords whatsoever.