I was unable to find a final resolution of this (and doesn't seem to work for me on 10.8.2 and sage5.5). The certtool errors are the same. Is there a ticket on this (I couldn't find one) or a work around?
On Wednesday, October 31, 2012 8:51:26 AM UTC-4, Ivan Andrus wrote: > > On Oct 31, 2012, at 12:40 PM, Andreas Paeffgen wrote: > > On 2012-10-31 09:32:28 +0000, Ivan Andrus said: > >> Hi Ivan, > >> this change works only have the way. The option secure=False works > great; secure=True gives me a lot of errors / troubles. > >> Should i open a ticket in http://trac.sagemath.org/sage_trac/ ? I > could not find a category for the sage.app version. > >> Sure, you can open a ticket. There is no category for Sage.app, so > make sure to cc me (iandrus) when you create a ticket. FWIW, I can't start > one from the command with secure=True since it complains about pyOpenSSL. > This is documented in the README included with Sage, so you may have to > follow the instruction there if you haven't already. Does it work from the > command line? > >> Also i use sage 5.3. On the track system i found just 5.4 and higher. > >> That's meant for when the fix will be available, not for the version it > was reported against. > >> -Ivan > > > > Hi Ivan, > > on the command line there is a certtool problem. The command certtool > --generate-self-signed --template /Users/myuser/.sage/notebook/cert.cfg > --load-privkey /Users/myuser/.sage/notebook/private.pem --outfile > /Users/myuser/.sage/notebook/public.pem does not work. > > > > From certool h > > certtool > > usage: > > Create a keypair and cert: certtool c [options] > > Create a CSR: certtool r outFileName [options] > > Verify a CSR: certtool v infileName [options] > > Create a system Identity: certtool C domainName [options] > > Import a certificate: certtool i inFileName [options] > > Display a certificate: certtool d inFileName [options] > > Import a CRL: certtool I inFileName [options] > > Display a CRL: certtool D inFileName [options] > > Display certs and CRLs in keychain: certtool y [options] > > > > So even when i first run certtool manually to create a private.pem it > does not work. notebook(secure=True) always invokes the wrong certtool > commands. > > > > > > Location of certtool is /usr/bin/certtool > > No version info available > > Best regards > > Andreas > > > It looks like the OS X and GNU versions of certtool differ greatly in > their usage. But has noone run secure servers on OS X? I wonder if you > and I are missing something. I don't see any open trac tickets regarding > certtool, nor even any recently closed ones. > > Does anyone else know what should be done here? > > -Ivan -- You received this message because you are subscribed to the Google Groups "sage-support" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support?hl=en.
