On Sun, Feb 12, 2012 at 04:27, Michael Orlitzky <mich...@orlitzky.com> wrote: > Rather than build SSL support into the application servers, everyone > deployed apache or nginx as an SSL proxy in front of them. Could this work > for the sage notebook? > > The notebook would always run on e.g. localhost:8080 unencrypted, without > linking to OpenSSL. If someone wants to make his notebook server public, he > downloads nginx/apache and a tiny config file that proxies 0.0.0.0:8080 to > localhost:8080, possibly using SSL.
This sounds good to me. William was also musing about whether out-of-the-box SSL support in the notebook was really that important, a while ago: https://groups.google.com/d/topic/sage-devel/Jl11JxIb2E8/discussion . IMO we can extend that reasoning to whether SSL support in the notebook is really that important at all, out-of-the-box or otherwise. As long as we provide instructions on how to use nginx as a backend to provide SSL, we're not really losing functionality, just increasing inconvenience a bit for those who want to use SSL. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
