2 ms·
I'm using a patched version of wetty (https://github.com/esantoro/wetty https://github.com/esantoro/wetty), a web-based ssh terminal. The patches add the possi
by znpy 7y ago
I'm using a patched version of wetty (https://github.com/esantoro/wetty https://github.com/esantoro/wetty), a web-based ssh terminal.
The patches add the possibility of specifying a different target host, whereas the original wetty only allowed connecting to the host currently executing wetty.
I run it in a container, I've skimmed the source code and it disarmingly simple: it performs a forkpty call to spawn the ssh client binary and then the connection goes on as the forked process is forwarded raw characters.
Under the security POV is kinda okay as everything is tunneled via TLS and the endpoint is (at least in my installation) not advertised very much. I check the server access logs from time to time and I don't see any activity besides my accesses.
In general a web based terminal is very handy, I wouldn't dismiss such a technology so quickly and superficially.