> > I guess it is because of this: > https://bugzilla.mozilla.org/show_bug.cgi?id=360126 . Server uses 512-bit > key, and Firefox requires at least 1024-bit key. (Of course it is a bug in > Firefox to not say clearly WHY it doesn't accept it!) > > https://sage.sis.uta.fi works with Firefox 33. I guess that server admin > should generate a new key or, even better, get a real certificate. > > A workaround is probably something that starts with "Write 'about:config' > to address bar and search for...". > > 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.
- kcrisman -- 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 sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
