["Followup-To:" header set to gmane.comp.mathematics.sage.notebook.] On 2012-11-30, Dima Pasechnik <dimp...@gmail.com> wrote: > ------=_Part_464_11607180.1354257615111 > Content-Type: text/plain; charset=ISO-8859-1 > > this is now > https://github.com/sagemath/sagenb/issues/117 > > On Friday, 30 November 2012 12:25:45 UTC+8, Kwankyu wrote: >> >> Thanks Dima. >> >> There is also a related issue. The Sage notebook generates 512 bits rsa >> private key by default, at least on my system. This key is considered weak >> by the latest Chrome, and it does not accept the certificate containing the >> weak key. Using 1024 bits rsa key, I succeeded to make Chrom to accept the >> self-signed certificate. what is your system? As you can see from the lines 417-433 of https://github.com/sagemath/sagenb/edit/master/sagenb/notebook/run_notebook.py it depends upon the OS how the cert is generated.
Dima -- You received this message because you are subscribed to the Google Groups "sage-support" group. To post to this group, send email to sage-support@googlegroups.com. To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support?hl=en.
