On Thu, Feb 12, 2009 at 12:37:47AM +0100, <Eriol>: ~> sha1 and md5 are already in the stdlib.
Then it's better to use them. What about the shrinking factor? Isn't it better to just use openssl as an external library to minimize the size of our python binary? Keep in mind that crypto stuff couldn't be necessary for the ntk protocol[*], but only for ANDNA, Carciofo. Thus, it would be possible to run ntkd without openssl. This could be of some benefit for some small Acces Points. [*] Unless we implement the secure QSPN and require it as necessary. What is the most size-savy solution? ~> On Wednesday 11 February 2009 14:49:11 Francesco Losciale wrote: ~> > the purpose is to implement a small lib/crypto.py module that could be ~> > usefull for several jobs, such as the ANDNA cryptographic ~> ~> I don't think we need a crypto.py, why should we reinvent the wheel? :) Just organizing the code. Take a look at crypto.[ch] (old C version). It is a thin wrapper to openssl. Advantages: 1) ntk-friendly function names 2) more independent from any real crypto library you're going to use. (f.e. we can use sha1 and md5 from the stdlib and the rest from Openssl) ~> For RSA stuff we can use the production ready and well tested code of ~> m2crypto. yea. Yesterday, we've arrived at the same conclusion: < AlpT_> maybe http://wiki.python.org/moin/M2Crypto is what we are looking for < AlpT_> it has the same API of openssl < AlpT_> it uses SWIG to interface with openssl < jnz_> M2Crypto is very cool ;) -- :wq! "I don't know nothing" The One Who reached the Thinking Matter '.' [ Alpt --- Freaknet Medialab ] [ GPG Key ID 441CF0EE ] [ Key fingerprint = 8B02 26E8 831A 7BB9 81A9 5277 BFF8 037E 441C F0EE ] _______________________________________________ Netsukuku mailing list [email protected] http://lists.dyne.org/mailman/listinfo/netsukuku
