Latest update.
This commit is contained in:
@@ -3,7 +3,8 @@
|
||||
=head1 NAME
|
||||
|
||||
pem_password_cb,
|
||||
PEM_read_bio_PrivateKey, PEM_read_PrivateKey, PEM_write_bio_PrivateKey,
|
||||
PEM_read_bio_PrivateKey_ex, PEM_read_bio_PrivateKey, PEM_read_PrivateKey_ex,
|
||||
PEM_read_PrivateKey, PEM_write_bio_PrivateKey,
|
||||
PEM_write_bio_PrivateKey_traditional, PEM_write_PrivateKey,
|
||||
PEM_write_bio_PKCS8PrivateKey, PEM_write_PKCS8PrivateKey,
|
||||
PEM_write_bio_PKCS8PrivateKey_nid, PEM_write_PKCS8PrivateKey_nid,
|
||||
@@ -33,8 +34,14 @@ PEM_write_bio_PKCS7, PEM_write_PKCS7 - PEM routines
|
||||
|
||||
typedef int pem_password_cb(char *buf, int size, int rwflag, void *u);
|
||||
|
||||
EVP_PKEY *PEM_read_bio_PrivateKey_ex(BIO *bp, EVP_PKEY **x, pem_password_cb *cb,
|
||||
void *u, OPENSSL_CTX *libctx,
|
||||
const char *propq);
|
||||
EVP_PKEY *PEM_read_bio_PrivateKey(BIO *bp, EVP_PKEY **x,
|
||||
pem_password_cb *cb, void *u);
|
||||
EVP_PKEY *PEM_read_PrivateKey_ex(FILE *fp, EVP_PKEY **x, pem_password_cb *cb,
|
||||
void *u, OPENSSL_CTX *libctx,
|
||||
const char *propq);
|
||||
EVP_PKEY *PEM_read_PrivateKey(FILE *fp, EVP_PKEY **x,
|
||||
pem_password_cb *cb, void *u);
|
||||
int PEM_write_bio_PrivateKey(BIO *bp, const EVP_PKEY *x, const EVP_CIPHER *enc,
|
||||
@@ -168,6 +175,9 @@ brevity the term "B<I<TYPE>> functions" will be used below to collectively
|
||||
refer to the B<PEM_read_bio_I<TYPE>>(), B<PEM_read_I<TYPE>>(),
|
||||
B<PEM_write_bio_I<TYPE>>(), and B<PEM_write_I<TYPE>>() functions.
|
||||
|
||||
Some operations have additional variants that take a library context I<libctx>
|
||||
and a property query string I<propq>.
|
||||
|
||||
The B<PrivateKey> functions read or write a private key in PEM format using an
|
||||
EVP_PKEY structure. The write routines use PKCS#8 private key format and are
|
||||
equivalent to PEM_write_bio_PKCS8PrivateKey().The read functions transparently
|
||||
@@ -307,6 +317,12 @@ arbitrary data to be passed to the callback by the application
|
||||
I<must> return the number of characters in the passphrase or -1 if
|
||||
an error occurred.
|
||||
|
||||
Some implementations may need to use cryptographic algorithms during their
|
||||
operation. If this is the case and I<libctx> and I<propq> parameters have been
|
||||
passed then any algorithm fetches will use that library context and property
|
||||
query string. Otherwise the default library context and property query string
|
||||
will be used.
|
||||
|
||||
=head1 NOTES
|
||||
|
||||
The old B<PrivateKey> write routines are retained for compatibility.
|
||||
@@ -480,9 +496,12 @@ The old Netscape certificate sequences were no longer documented
|
||||
in OpenSSL 1.1.0; applications should use the PKCS7 standard instead
|
||||
as they will be formally deprecated in a future releases.
|
||||
|
||||
PEM_read_bio_PrivateKey_ex() and PEM_read_PrivateKey_ex() were introduced in
|
||||
OpenSSL 3.0.
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Copyright 2001-2019 The OpenSSL Project Authors. All Rights Reserved.
|
||||
Copyright 2001-2020 The OpenSSL Project Authors. All Rights Reserved.
|
||||
|
||||
Licensed under the Apache License 2.0 (the "License"). You may not use
|
||||
this file except in compliance with the License. You can obtain a copy
|
||||
|
||||
Reference in New Issue
Block a user