From a785b8d38a0110e34d59e838794973c4b37570b9 Mon Sep 17 00:00:00 2001 From: Arafat Abdussalam Date: Fri, 14 Oct 2022 02:59:34 -0700 Subject: [PATCH] I made the correction to the PR I resolved my previous commit as suggested --- docs/source/reference/websecurity.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/reference/websecurity.md b/docs/source/reference/websecurity.md index d9a9a397..9de4b38b 100644 --- a/docs/source/reference/websecurity.md +++ b/docs/source/reference/websecurity.md @@ -10,13 +10,13 @@ The **Security Overview** section helps you learn about: This overview also helps you obtain a deeper understanding of how JupyterHub works. -## Semi-trusted and Untrusted Users +## Semi-trusted and untrusted users JupyterHub is designed to be a _simple multi-user server for modestly sized groups_ of **semi-trusted** users. While the design reflects serving semi-trusted users, JupyterHub is not necessarily unsuitable for serving **untrusted** users. -Using JupyterHub with **untrusted** users entails more work by the +Using JupyterHub with **untrusted** users does mean more work by the administrator. Much care is required to secure a Hub, with extra caution on protecting users from each other as the Hub is serving untrusted users. @@ -41,7 +41,7 @@ To protect all users from each other, JupyterHub administrators must ensure that: - A user **does not have permission** to modify their single-user notebook server, - as well as: + including: - A user **may not** install new packages in the Python environment that runs their single-user server. - If the `PATH` is used to resolve the single-user executable (instead of