You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To offer a websocket JS-in-webpage-accessible shell server with auth. However at the moment, when i run the command like this it still accepts unauthenticated clients
The text was updated successfully, but these errors were encountered:
If you want to enforce specific prefix, you may want --restrict-uri option:
--restrict-uri <restrict_uri>
When serving a websocket, only accept the given URI, like `/ws`
This liberates other URIs for things like serving static files or proxying.
It does not mean the shell server would be secure.
You may want to handle auth upstream (i.e. on Nginx / Caddy). If you want shell access from browser, you may also find ttyd useful.
I would like to be able to do
To offer a websocket JS-in-webpage-accessible shell server with auth. However at the moment, when i run the command like this it still accepts unauthenticated clients
The text was updated successfully, but these errors were encountered: