>
> > Would you recommend putting this somewhere in the sagenb documentation?
> I
> > wasn't even aware of this .sage/notebook/ directory, since I'm not an
> admin.
>
> Hmm... Where? Maybe
>
> http://www.sagemath.org/doc/reference/notebook/sagenb/notebook/notebook_object.html
>
> could hav
On Thu, 30 Oct 2014, kcrisman wrote:
Would you recommend putting this somewhere in the sagenb documentation? I
wasn't even aware of this .sage/notebook/ directory, since I'm not an admin.
Hmm... Where? Maybe
http://www.sagemath.org/doc/reference/notebook/sagenb/notebook/notebook_object.html
>
> 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
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
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?
>
>
> > 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
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 i
> 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 ... ?
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 clarific
>
> 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.
On Mon, 27 Oct 2014, mjs wrote:
With the recent release of Firefox 33 (now shipped to Fedora, coming
soon to an OS near you), I can no longer connect to my Sage 6.3 server.
The error I get is:
An error occurred during a connection to sage.math.clemson.edu:34567.
The key does not support the
Am 2014-10-27 um 19:08 schrieb mjs:
> With the recent release of Firefox 33 (now shipped to Fedora, coming
> soon to an OS near you), I can no longer connect to my Sage 6.3 server.
> The error I get is:
>
> An error occurred during a connection to sage.math.clemson.edu:34567.
> The key does not s
12 matches
Mail list logo
