Quantcast
Channel: Comments on Improving the pynacl build process
Browsing all 7 articles
Browse latest View live

By: Andrew Sutherland

I fear this is too late to be any use, but for deuxdrop, I created a waf wscript that builds nacl. Its decisions of what algorithms to use are based on poor python heuristics, but it tries to otherwise...

View Article



By: warner

Ah, yeah, wish I’d seen that a day earlier :). At least it confirms what I deduced from the ‘do’ script. I think the distutils-based scheme in my “minimal” branch is still a good way to go.. I’ll...

View Article

By: warner

So, to figure out how to build alternate versions of the ed25519 signature code (like the amd64-51-30k version), I first needed to learn what compiler flags would work, so I started the SUPERCOP...

View Article

By: warner

Also an interesting datapoint: Matthew Dempsky’s pure-python Curve25519 code, from page 6+7 of http://cr.yp.to/papers.html#naclcrypto , runs in about 22ms on this same laptop. So for human-initiated...

View Article

By: Sean Lynch

Wow, I’ve been blissfully ignorant that anyone was using pynacl. I somehow completely missed an email notification about a pull request from k3d3 back in December and didn’t realize until today when I...

View Article


By: Sean Lynch

I wonder if it only worked for me (given the PIC problems) because I am on a Mac.

View Article

By: warner

an update: the SUPERCOP suite finally finished, after 15 days! On my Athlon64 box, it got passing results with -m32 (but not -m64), an -march= in the set [athlon, barcelona, core2, i386, i486, k6,...

View Article
Browsing all 7 articles
Browse latest View live




Latest Images