On Jan 12, 2012 7:43 AM, "Jason Grout" <jason-s...@creativetrax.com> wrote: > > On 1/12/12 3:20 AM, Robert Bradshaw wrote: >> >> It pains me a bit to say yes, but I agree with your assessment of the >> situation; it's needed only by the few (and the technically capable) >> and is a lot of weight for something that looks to always be an >> incomplete hack around not having OpenSSL on the system. Just make >> sure that it's clearly documented to that to run with secure=True >> (perhaps this could be renamed to ssl=True, so secure=False doesn't >> sound so bad) one needs to instal ssl before building Sage (or at >> least its Python). Setting up a public/multi-user server has larger >> security implications anyways (e.g. setting up workers in a VM or >> other trusted environment depending on the set of users). > > > How about changing it to protocol='https' instead of ssl=True or secure=True? Of course, the default would be protocol='http'
+1 > > Thanks, > > Jason > > > > -- > 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 -- 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
