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
Running web applications on multi-user systems (even behind a JupyterHub) requires that the web application supports some kind of authentication (this can be a token that has to be passed in the URL, as we know it from Jupyter/JupyterLab).
However, some applications lack this basic security and are accessible to anyone who can log into the multi-user system and access their port.
If these web applications would not use a port but a UNIX socket for internal communication with jhsingle-native-proxy, this security hole could be closed in a quite elegant way.
For jupyter-server-proxy this great feature was just recently added - jupyterhub/jupyter-server-proxy#321 and might be a starting point.
The text was updated successfully, but these errors were encountered:
Hello everyone,
Running web applications on multi-user systems (even behind a JupyterHub) requires that the web application supports some kind of authentication (this can be a token that has to be passed in the URL, as we know it from Jupyter/JupyterLab).
However, some applications lack this basic security and are accessible to anyone who can log into the multi-user system and access their port.
If these web applications would not use a port but a UNIX socket for internal communication with jhsingle-native-proxy, this security hole could be closed in a quite elegant way.
For jupyter-server-proxy this great feature was just recently added - jupyterhub/jupyter-server-proxy#321 and might be a starting point.
The text was updated successfully, but these errors were encountered: