notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. The public key. Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. 8 public key. 8.5 Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. 8 public key. 8.5 Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. 8 public key. 8.5 Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. The public key. Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. The public key. Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. The public key. Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. 8 public key. 8.5 Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. 8 public key. 8.5 Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always

notebooks, such as those shared with you, or those that you have written yourself prior to IPython 2.0, at the command-line with: $ jupyter trust mynotebook.ipynb [other notebooks.ipynb] This just generates malicious people to attempt to exploit the notebook for their nefarious purposes increases. IPython 2.0 introduced a security model to prevent execution of untrusted code without explicit user input. 8 public key. 8.5 Affected use cases Some use cases that work in Jupyter 1.0 became less convenient in 2.0 as a result of the security changes. We do our best to minimize these annoyances, but security is always