This is to make it possible for admins to enable password-less
auth at the expense of security.
In that situation:
Server <=> Wetty <=> Client
- Link between Wetty and the SSH Server is secured by SSH.
- Wetty knows a private key to connect to the SSH Server, using an SSH
User.
- Client only needs to know how to access Wetty to run commands
on the SSH Host.
- Client would not be able to retrieve the private key from Wetty to
login directly to the SSH Server.
This basically means that anything that reaches Wetty needs to be
trusted as it would be able to execute commands on the remote SSH server,
so admins should be really careful when using that feature.
* Added Apache configuration for proxifying wetty.
* Typo fix for Apache configuration.
* Updated procedure for starting wetty (use of bin/index.js instead of app.js)
* - Add help message
- Removed unnecesary ifs
* Moved to a module.
Add events:
* exit (code): Ssh process finished, informs the process exitcode.
* disconnect : Socket disconnected.
* Fix on previous commit
* Fix on previous commit
* Add a reconnect button on logout
Prior to this, the only way to return to a session after logging out or
login timeout was to manually reload the page. This gives you a nice
button to do it for you.
Ping @joshsamuelson
* Forgot the z-index
* Whoa, there's two copies?
Not sure why there are two index.html files, but...
* Forgot the z-index
Bertrand Roussel
Oleg Kurapov
Oleg Kurapov
Cian Butler
cbutler
mirtouf
nosemeocurrenada
Strubbl
butlerx
Imuli