Does your library wrap lower level routines from SSPI or OpenSSL or does it implement the SSL/TLS methods natively? For legal reasons, i don't want to export any crypto with my product but would rather use the crypto that is already present on the client machines. Therefore, I am looking for libs that wrap existing interfaces.

-reggie

The cryptographic algorithms used under the covers of the Security Library are mostly those that are distributed with the .NET framework, but the library does contain some other cryptographic implementations that do not ship with the .NET framework.

However, why would you worry about cryptographic export rules? Most countries have very liberal export laws regarding cryptography (including the US -- see http://www.rsasecurity.com/rsalabs/faq/6-4.html for details).