On Tue, 28 Oct 2014, kcrisman wrote:
This is a little hermetic for me. Are you all saying that sagenb using openssl is the problem, or that one needs to have it reconfigured to use better encryption, or that people running Sage servers need to buy certificates, or ... ? Thanks for any clarification.
Shortly: Shut down Sage. Say "mv .sage/notebook/ sage-keys-old". Start Sage. Say "notebook(secure=True, ...)". Now Sage generates new and longer certificate.
And now it will work with Firefox. But on the other hand, users will see warning about 1) self-signed certificate AND/OR 2) changed certificate. And if they learn to skip warnings like those, whole point of https degenerates.
-- Jori Mäntysalo -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
