Re: [jupyter] Blocking copy/paste functionality to JupyterHub

2018-02-21 Thread Roland Weber
Hello Jeremy. Blocking copy and paste is one of the main features that we wish to > achieve. Essentially, we would like to ensure that a JupyterHub notebook > user is able to use and modify their notebooks at will normally (via > typing, clicking and normal keystrokes), > When I write code, I

Re: [jupyter] Blocking copy/paste functionality to JupyterHub

2018-02-21 Thread Matthias Bussonnier
Thanks Jeremy, On 20 February 2018 at 16:41, Jeremy Ho wrote: > Hi Matthias, > > Thank you for your response. For some background context, the notebooks > will have access to sensitive data sources that we don't want to have > leaving the notebooks, and we also don't want to

Re: [jupyter] Blocking copy/paste functionality to JupyterHub

2018-02-21 Thread Michael Milligan
Hi Jeremy, Your original question made it sound like you might be using the notebook purely as a dashboard interface with some level of point-and-click interactivity. This should be doable using the advice you have already received, provided you have good control of your users work environment.

Re: [jupyter] Blocking copy/paste functionality to JupyterHub

2018-02-20 Thread Jeremy Ho
Hi Matthias, Thank you for your response. For some background context, the notebooks will have access to sensitive data sources that we don't want to have leaving the notebooks, and we also don't want to have users can inserting their own content into the environment. Blocking copy and paste

Re: [jupyter] Blocking copy/paste functionality to JupyterHub

2018-02-20 Thread Matthias Bussonnier
Hello Jeremy, Thanks for your question, A few Questions: is copy and past the only thing you want to block ? Do you sill want users to be able to modify notebooks by typing ? Is the a specific requirement/certification you need to have ? A couple of clarification as well: JupyterHub act only as

[jupyter] Blocking copy/paste functionality to JupyterHub

2018-02-19 Thread Jujaga
Hi all, Our group is currently leveraging zero-to-jupyterhub-k8s in order to provide Notebooks to a multi-user environment via Kubernetes. However, we also have a business requirement where we must prevent users from copying information out of the Notebooks, as well as preventing the insertion of