Hi devs,
we develop new engine and we have problem with save/load information about
keys on this engine (name, type of key, IP address, etc.) I know this
attributes are for every engines different.
I think we can do new ASN1 structre for all engines like this (excuse me
ASN1 code)
Engine ::= SEQUENCE {
name String, -- name of engine as is in OpenSSL
dataType OID OPTIONAL, -- RSA key | DSA key | certifcate | ...
data EngineData -- engine specifically data
}
In EngineData all engine developer can put own useful data. Developer create
two functions d2i and i2d for this.
this ASN1 can be transfer to PEM with new headers like -----BEGIN OPENSSL
ENGINE-----
now we can easy load EVP_PKEY through PEM_read_bio_Private_Key(bio, ...) /
d2i_Private_Key_bio(bio, ) in bio can be simply OpenSSL RSA key or some
Engine Key.
This method can easy use for load private keys or for some other data, like
certificates, CA certificates from engine.
Martin
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
