On Wed, 2016-11-23 at 09:39 +0100, Tomas Mraz wrote: > > I also would not be too much worried - the API call should not be > completely universal - the application should know whether it is > loading a certificate or private key. It should just be able to use a > single call to load a certificate in PEM, DER, or whatever other > possible data format. The same for private keys, etc.
Well, except in the case where the application asks to use a PKCS#12 file as the identity. In which case you want to load cert, key, and supporting cert chain all from the same place. And you often have a PEM file which contains both the certificate and the private key. But yes, generally you *know* what you're looking for. -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
-- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
