Crypto boundary and certification

From Libreswan
Revision as of 12:03, 5 June 2013 by Paul Wouters (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Paul to document, explain and implement the crypto boundary


Is there a readonly and writeonly path for crypto ?

NSS debugging / logging should be fixed before this, so we don't need to change any crypto files.


This also depends on putting CRLs/certs into nss, and not using the "openssl" methods of loading from /etc/ipsec.d/


so ifdef NSS/OPENSSL needs to happen before this.


nss errors returns numbers, and you need to do a call to nss to get the string message length, then allcoate that space and send it to another nss function.

we need an nss module, that is thread safe, to deal with the logging.