On 5/27/07, Yi Qiang <[EMAIL PROTECTED]> wrote: > I will look into what it's going to take to get DSAGE to use gnutls. > The python wrapper did not compile under os x so that will need some > work.
I tried for over an hour just to get gnutls to compile at all under OSX; all the things it depends on would build, but I simply couldn't get it to build. An hour isn't that long and I was tired, but I suspect building gnutls on osx might be harder than expected. I've put the relevant spkg's here in case anybody else wants to try: http://sage.math.washington.edu/home/was/tmp/gnutls > However I checked out the examples directory and it looks like > swapping it over to TLS will be fairly easy. What is not very > assuring though is that I can not find any examples online of people > using twisted + gnutls. If we want to port the notebook over to use > twisted as the backend (or whatever else really) and provide SSL then > we might be running into a lot of trouble because it's simply not > going to be as well tested as openssl. True. But that's just the way it is. Simple question: Can you make an insecure version of DSAGE that doesn't rely on ssl at all? Then I can release a new version of SAGE without openssl in it, without any degredation in performance (except ssl won't work). The other option is that I release a new SAGE with DSAGE nonfunctional until this ssl problem gets resolved. -- William -- William Stein Associate Professor of Mathematics University of Washington http://www.williamstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
