Just following myself up to note that yes, moving .sage/notebook out of the way and restarting the server did regenerate keys and Firefox was able to connect successfully.
Thanks for your help. On Wednesday, October 29, 2014 1:02:02 PM UTC-4, mjs wrote: > > I'm the OP and I run the Sage server at sage.math.clemson.edu. So my > question is, how to get my server to regenerate a proper self-signed key. > I don't have the budget at the moment for a real key. > > (1) So moving the server's .sage/notebook directory will generate new keys > that are long enough? > (2) If I do get a real key, is that where to put it? > > Thanks. > > On Wednesday, October 29, 2014 8:45:44 AM UTC-4, jori.ma...@uta.fi wrote: >> >> On Wed, 29 Oct 2014, kcrisman wrote: >> >> > I see, so the server will indeed automatically generate the "correct" >> > keys, but if it previously generated them and is still using the same >> > ones then it might not. Thanks for clarifying. >> >> But what Sage should do? If somebody manually runs notebook(), then it >> could just ask something like "Current keys are... generate new? [y/N]". >> But what if user runs sage -c 'notebook(...)'? Force to use >> "--allow-short-ssl-key" -argument? >> >> > Well, yes. This is true for lots of websites... but obtaining "real" >> > certificates is not an easy proposition, right? (I mean not *hard*, >> but >> > requires at least some money and other registration/whatnot?) >> >> You asked about sage.math.clemson.edu, i.e. part of Clemson university. >> Isn't there any computer centre to help with certificates? >> >> -- >> 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 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.
