What about using RSA's BSAFE crypto packages?
jason lawrence
https://community.emc.com/community/edn/rsashare
It would probably be pretty easy to Python SWIG wrapper their
libraries. Do you guys think this would be a more suitable option
compared to OpenSSL and NSS? I personally deal with NSS and it sucks
in epic proportions... I mostly use OpenSSL at work, but I've heard
our developers say that they like the BSAFE libraries...
geremy condra
> I noticed that EMC (RSA) has opened up their BSAFE crypto libraries...
>
> https://community.emc.com/community/edn/rsashare
I don't actually see any kind of license terms, am I missing something?
> It would probably be pretty easy to Python SWIG wrapper their
> libraries. Do you guys think this would be a more suitable option
> compared to OpenSSL and NSS? I personally deal with NSS and it sucks
> in epic proportions... I mostly use OpenSSL at work, but I've heard
> our developers say that they like the BSAFE libraries...
I'm pretty sure I wouldn't want to use swig for this stuff. Full disclosure,
I'm writing bindings using ctypes right now - http://gitorious.org/evpy -
but I think the best way to go in general is to do the C-API bindings
by hand. Besides that, I have no idea about this library- any other
opinions on it?
Geremy Condra
Mike Ivanov
> On Sat, Mar 27, 2010 at 11:55 PM, jason lawrence <clif...@gmail.com> wrote:
>> I noticed that EMC (RSA) has opened up their BSAFE crypto libraries...
>>
>> https://community.emc.com/community/edn/rsashare
>
> I don't actually see any kind of license terms, am I missing something?
At this page: https://community.emc.com/docs/DOC-3459 (you have to
register to read the license).
It's not quite open source: you can't redistribute the lib. Plus they
reserve the right to audit your records to "verify compliance with the
agreement."
Of course, any kind benchmarking is prohibited.
This is acceptable if you are a government or a large corp, but I
can's see how this can work for a broader public.
Mike