Peter Gutmann
2017-03-24 08:10:20 UTC
cryptlib currently opens keysets as disk files, but I've had a request from
someone for an in-memory equivalent, which takes the file-based:
cryptKeysetOpen( &keyset, CRYPT_UNUSED, CRYPT_KEYSET_FILE, filename, CRYPT_KEYOPT_xxx );
and turns it into:
cryptOpenMemKeyset( &keyset, CRYPT_UNUSED, buffer, bufferSize, CRYPT_KEYOPT_xxx );
Would there be any general demand for this? I'm trying to gauge whether it's
worth adding as a standard API feature, are there people who would
specifically need this (rather than just "it sounds like a good idea to add
it")?
Peter.
_______________________________________________
Cryptlib mailing list
***@mbsks.franken.deAdministration via Mail: cryptlib-***@mbsks.franken.de
Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/
http://news.gmane.org/gmane.comp.encryption.cryptlib
Posts from non-subscribed addresses are blocked to prevent spam, pleas
someone for an in-memory equivalent, which takes the file-based:
cryptKeysetOpen( &keyset, CRYPT_UNUSED, CRYPT_KEYSET_FILE, filename, CRYPT_KEYOPT_xxx );
and turns it into:
cryptOpenMemKeyset( &keyset, CRYPT_UNUSED, buffer, bufferSize, CRYPT_KEYOPT_xxx );
Would there be any general demand for this? I'm trying to gauge whether it's
worth adding as a standard API feature, are there people who would
specifically need this (rather than just "it sounds like a good idea to add
it")?
Peter.
_______________________________________________
Cryptlib mailing list
***@mbsks.franken.deAdministration via Mail: cryptlib-***@mbsks.franken.de
Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/
http://news.gmane.org/gmane.comp.encryption.cryptlib
Posts from non-subscribed addresses are blocked to prevent spam, pleas