On Mon, 29 Mar 2010, Casey Ransberger wrote:
What's the usual best practice around crypto in Squeak? Usually rolling one's own crypto is a ridonculously bad idea so... do folks usually pipe things to and from the cryptography of the underlying OS using OSProcess?
There was a Cryptography team a few years ago with a few devs and big plans, but the team disappeared somehow... Anyway we have some usable code and a lot of half baked stuff here: http://www.squeaksource.com/Cryptography.html Start with Cryptography-cmm.11.mcz if you're interested.
People are usually looking for three stuff: - hashes (MD5, SHA1, etc). These work pretty well. I think MD5 should be added to Squeak in the future. - SSL. It's somewhat broken (has issues with certificates IIRC) and really slow if used without the DESPlugin. The Cobalt developers forked the Cryptography package and fixed lots of stuff about SSL. But if you just want to fetch a few web pages, you better try curl first. - SSH. That's pre-alpha. :)
Levente