On Saturday, May 26, 2018 at 12:58:29 AM UTC+2, Nils Bruin wrote:
>
> Would you have particular words to say to sysadmins who get worried about
> users opening up services on all kinds of ports? (and this sysadmin could
> be me) -- of course, it also requires the ability to punch the right holes
On Friday, May 25, 2018 at 3:33:47 PM UTC-7, Volker Braun wrote:
>
> I'm not saying anything against ssh tunnel. Though running jupyter
> remotely with a self-signed cert and authentication with a fixed token
> handles network disconnect/reconnects better...
>
Would you have particular words
I'm not saying anything against ssh tunnel. Though running jupyter remotely
with a self-signed cert and authentication with a fixed token handles
network disconnect/reconnects better...
I'm not particularly happy with the state of multi-user jupyterhub, there
is a fundamental bug in the PAM
On Friday, May 25, 2018 at 1:24:39 PM UTC-7, Volker Braun wrote:
>
> On Friday, May 25, 2018 at 7:02:19 PM UTC+2, Nils Bruin wrote:
>>
>> Since your approach requires the device to run ssh, a much more portable
>> option is to run the jupyter server on the remote machine as well
>> (listening on
On Friday, May 25, 2018 at 7:02:19 PM UTC+2, Nils Bruin wrote:
>
> Since your approach requires the device to run ssh, a much more portable
> option is to run the jupyter server on the remote machine as well
> (listening on localhost) and use ssh to forward the relevant port so that a
> local
On Friday, May 25, 2018 at 5:59:55 AM UTC-7, Emmanuel Charpentier wrote:
>
> Dear list,
>
> [ This goes to sage-support becaus I do not know if this is already
> possible with our current kernel. Please redirect to sage-devel if you
> think it more appropriate... ]
>
> Re-hashing the SageTeX
