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
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 Chro
On 2012-11-30, Kwankyu wrote:
> --=_Part_809_10674594.1354242126940
> Content-Type: text/plain; charset=ISO-8859-1
>
> In the meantime, I investigated this issue a bit more. The root of the
> problem is the too large value of expiration_days ="1" in
> ".sage/notebook/cert.cfg", which is
In the meantime, I investigated this issue a bit more. The root of the
problem is the too large value of expiration_days ="1" in
".sage/notebook/cert.cfg", which is automatically generated in the
notebook.setup() command. I tried to change the value like 8999. Then the
generated certificate
Hi all,
I noticed there is a problem with the Sage's self-signed certificate for my
own server. See the validity date. Why is it 2004? Thanks for an answer in
advance. My system is Sage 5.4.1 on Ubuntu Server.
X.509 Certificate Information:
Version: 3
Serial Number (hex): 1f36ede1
Validity:
Not
On 11/29/12 2:04 PM, Andre, der Besonnene wrote:
I guess I've forgotten to mention that sage works when the directoryname
has the suffix *.sagenb
so this works: sage: notebook(directory="/home/sage/s.sagenb",interface='')
this doesn't work: sage: notebook(directory="/home/sage/s",interface='')
I guess I've forgotten to mention that sage works when the directoryname
has the suffix *.sagenb
so this works: sage: notebook(directory="/home/sage/s.sagenb",interface='')
this doesn't work: sage: notebook(directory="/home/sage/s",interface='')
When the given directory doesn't exist, one is c
On Thursday, November 29, 2012 3:44:40 AM UTC-5, Keshav Kini wrote:
>
> "WM Chung" > writes:
> > I would like to know if I can install multiple versions of SAGE under
> > the same system. Now I have a VM of Ubuntu and Sage 5.3 is built from
> > source code. Can I build Sage 5.4 in different di
On Wednesday, November 28, 2012 9:27:58 PM UTC+1, Simon King wrote:
>
> Hi Georgi,
>
> On 2012-11-28, Georgi Guninski >
> wrote:
> > Probably the problem is in Singular.
>
> Probably not. If I am not mistaken, Singular is involved in polynomial
> factorisation over *finite* fields.
>
I agree
"WM Chung" writes:
> I would like to know if I can install multiple versions of SAGE under
> the same system. Now I have a VM of Ubuntu and Sage 5.3 is built from
> source code. Can I build Sage 5.4 in different directory in the same
> Ubuntu VM ? Can I keep the Sage 5.3 and not remove it ?
That
On Thu, 29 Nov 2012, WM Chung wrote:
I would like to know if I can install multiple versions of SAGE under the
same system. Now I have a VM of Ubuntu and Sage 5.3 is built from source
code. Can I build Sage 5.4 in different directory in the same Ubuntu VM ?
Can I keep the Sage 5.3 and not remove
Hi,
I would like to know if I can install multiple versions of SAGE under the
same system. Now I have a VM of Ubuntu and Sage 5.3 is built from source
code. Can I build Sage 5.4 in different directory in the same Ubuntu VM ?
Can I keep the Sage 5.3 and not remove it ?
Thanks.
W.M. Chung
12 matches
Mail list logo
