William Stein wrote: > On Sun, May 31, 2009 at 5:34 AM, Dr. David Kirkby > <david.kir...@onetel.net> wrote:
>> 1) sage-4.0.rc0 >> >> hangs when generating the private key: >> >> drkir...@kestrel:[~/sage/sage-4.0.rc0] $ ./sage >> 2) Using 4.0.rc1 I get a different problem - see below. > > That's caused by you killing (1) above when it wasn't done. By the > way, for (1) how long did you wait -- for me I had to wait quite a > while for the certificate to be generated. > Try deleting $HOME/.sage and starting over. William, I had done a rm -r on $HOME/.sage before posting those results - that does not help matters. certtool runs from the command line in 30 seconds or so on my machine. It was left running overnight (about 6 hours) in Sage and still would not generate the keys. So I believe it really has hung. I've now tried the 3.4.2 binary I downloaded from the Sage web site, in addition to 4.0.rc0 and 4.0.rc1 both of which I compiled myself from source. In summary: Using the unsecured 'notebook()' on the Blade 2000, which runs Solaris 10 update 6. 1) sage-3.4.2 - no error message, but no server on port 8000 2) sage-4.0.rc0 - no error message, but no server on port 8000 3) sage-4.0.rc1 - no error message, but no server on port 8000 Using the secure 'notebook(secure=True)' on the Blade 2000. 4) sage-3.4.2 - no error message, but hangs generating keys. 5) sage-4.0.rc0 - no error message, but hangs generating keys. 6) sage-4.0.rc1 - generates the traceback I showed. In each case, $HOME/.sage was removed before running any test. Running 'diff' I see something interesting. There are no changes between the two run_notebook.py files in sage-3.4.2 and sage-4.0.rc0, which probably explains why I get the same result. But there are changes in run_notebook.py between sage-4.0.rc0 and sage-4.0.rc1, which probably accounts for the traceback I get in sage-4.0.rc1. drkir...@kestrel:[~/sage] $ diff ./sage-4.0.rc1/devel/sage-main/sage/server/notebook/run_notebook.py ./sage-4.0.rc0/devel/sage-main/sage/server/notebook/run_notebook.py 36,46c36,41 < < try: < import dsage.all < print "Using dsage certificates." < dsage = os.path.join(DOT_SAGE, 'dsage') < sage.dsage.all.dsage.setup() < shutil.copyfile(dsage + '/cacert.pem', private_pem) < shutil.copyfile(dsage + '/pubcert.pem', public_pem) < except ImportError: < pass < --- > print "Using dsage certificates." > dsage = os.path.join(DOT_SAGE, 'dsage') > import sage.dsage.all > sage.dsage.all.dsage.setup() > shutil.copyfile(dsage + '/cacert.pem', private_pem) > shutil.copyfile(dsage + '/pubcert.pem', public_pem) I can see that to generate the private key, the following is being executed: 'certtool --generate-privkey --outfile /export/home/drkirkby/.sage/dsage/cacert.pem' what would be used to generate the public key? Perhaps I can generate this manually, outside of Sage, and get Sage to use them. I can't seem to find the relavant bit of code myself. Dave --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
