Lines Matching full:s0
274 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
332 …functions described on this page that have a \fI\s-1TYPE\s0\fR of \fB\s-1DH\s0\fR, \fB\s-1DSA\s0\fR
333 and \fB\s-1RSA\s0\fR are deprecated. Applications should use \fBOSSL_ENCODER_to_bio\fR\|(3) and
336 The \s-1PEM\s0 functions read or write structures in \s-1PEM\s0 format. In
337 this sense \s-1PEM\s0 format is simply base64 encoded data surrounded
341 \&\fB\s-1PEM FUNCTION ARGUMENTS\s0\fR section.
344 brevity the term "\fB\f(BI\s-1TYPE\s0\fB\fR functions" will be used below to collectively
345 refer to the \fBPEM_read_bio_\f(BI\s-1TYPE\s0\fB\fR(), \fBPEM_read_\f(BI\s-1TYPE\s0\fB\fR(),
346 \&\fBPEM_write_bio_\f(BI\s-1TYPE\s0\fB\fR(), and \fBPEM_write_\f(BI\s-1TYPE\s0\fB\fR() functions.
356 to the relevant \s-1PEM\s0 function. See the \*(L"\s-1EXAMPLES\*(R"\s0 section below.
358 The \fBPrivateKey\fR functions read or write a private key in \s-1PEM\s0 format using
359 an \s-1EVP_PKEY\s0 structure. The write routines use PKCS#8 private key format and are
368 key in an \s-1EVP_PKEY\s0 structure in PKCS#8 EncryptedPrivateKeyInfo format using
370 specifies the encryption algorithm to use: unlike some other \s-1PEM\s0 routines the
371 encryption is applied at the PKCS#8 level and not in the \s-1PEM\s0 headers. If
372 \&\fIcipher\fR is \s-1NULL\s0 then no encryption is used and a PKCS#8 PrivateKeyInfo
378 to use is specified in the \fInid\fR parameter and should be the \s-1NID\s0 of the
379 corresponding \s-1OBJECT IDENTIFIER\s0 (see \s-1NOTES\s0 section).
381 The \fB\s-1PUBKEY\s0\fR functions process a public key using an \s-1EVP_PKEY\s0
385 The \fBRSAPrivateKey\fR functions process an \s-1RSA\s0 private key using an
386 \&\s-1RSA\s0 structure. The write routines uses traditional format. The read
388 functions but an error occurs if the private key is not \s-1RSA.\s0
390 The \fBRSAPublicKey\fR functions process an \s-1RSA\s0 public key using an
391 \&\s-1RSA\s0 structure. The public key is encoded using a PKCS#1 RSAPublicKey
394 The \fB\s-1RSA_PUBKEY\s0\fR functions also process an \s-1RSA\s0 public key using
395 an \s-1RSA\s0 structure. However, the public key is encoded using a
397 key is not \s-1RSA.\s0
399 The \fBDSAPrivateKey\fR functions process a \s-1DSA\s0 private key using a
400 \&\s-1DSA\s0 structure. The write routines uses traditional format. The read
402 functions but an error occurs if the private key is not \s-1DSA.\s0
404 The \fB\s-1DSA_PUBKEY\s0\fR functions process a \s-1DSA\s0 public key using
405 a \s-1DSA\s0 structure. The public key is encoded using a
407 key is not \s-1DSA.\s0
409 The \fBParameters\fR functions read or write key parameters in \s-1PEM\s0 format using
410 an \s-1EVP_PKEY\s0 structure. The encoding depends on the type of key; for \s-1DSA\s0 key
411 parameters, it will be a Dss-Parms structure as defined in \s-1RFC2459,\s0 and for \s-1DH\s0
413 only exist for the \f(BI\s-1BIO\s0\fI type\fR.
415 The \fBDSAparams\fR functions process \s-1DSA\s0 parameters using a \s-1DSA\s0
417 as defined in \s-1RFC2459.\s0
419 The \fBDHparams\fR functions process \s-1DH\s0 parameters using a \s-1DH\s0
432 write functions use \fB\s-1CERTIFICATE REQUEST\s0\fR in the header whereas
433 the \fBX509_REQ_NEW\fR functions use \fB\s-1NEW CERTIFICATE REQUEST\s0\fR
437 The \fBX509_CRL\fR functions process an X509 \s-1CRL\s0 using an X509_CRL
440 The \fB\s-1PKCS7\s0\fR functions process a PKCS#7 ContentInfo using a \s-1PKCS7\s0
444 The \s-1PEM\s0 functions have many common arguments.
446 The \fIbp\fR \s-1BIO\s0 parameter (if present) specifies the \s-1BIO\s0 to read from
449 The \fIfp\fR \s-1FILE\s0 parameter (if present) specifies the \s-1FILE\s0 pointer to
452 The \s-1PEM\s0 read functions all take an argument \fI\f(BI\s-1TYPE\s0\fI **x\fR and return
453 a \fI\f(BI\s-1TYPE\s0\fI *\fR pointer. Where \fI\f(BI\s-1TYPE\s0\fI\fR is whatever structure the fu…
454 uses. If \fIx\fR is \s-1NULL\s0 then the parameter is ignored. If \fIx\fR is not
455 \&\s-1NULL\s0 but \fI*x\fR is \s-1NULL\s0 then the structure returned will be written
456 to \fI*x\fR. If neither \fIx\fR nor \fI*x\fR is \s-1NULL\s0 then an attempt is made
457 to reuse the structure at \fI*x\fR (but see \s-1BUGS\s0 and \s-1EXAMPLES\s0 sections).
459 returned (or \s-1NULL\s0 if an error occurred).
461 The \s-1PEM\s0 functions which write private keys take an \fIenc\fR parameter
463 at the \s-1PEM\s0 level. If this parameter is set to \s-1NULL\s0 then the private
467 phrase used for encrypted \s-1PEM\s0 structures (normally only private keys).
469 For the \s-1PEM\s0 write routines if the \fIkstr\fR parameter is not \s-1NULL\s0 then
473 If the \fIcb\fR parameters is set to \s-1NULL\s0 and the \fIu\fR parameter is not
474 \&\s-1NULL\s0 then the \fIu\fR parameter is interpreted as a \s-1NUL\s0 terminated string
475 to use as the passphrase. If both \fIcb\fR and \fIu\fR are \s-1NULL\s0 then the
480 in a \s-1GUI\s0 application) so an alternative can be supplied. The callback
492 value as the \fIu\fR parameter passed to the \s-1PEM\s0 routine. It allows
494 (for example a window handle in a \s-1GUI\s0 application). The callback
497 is a string, it is not \s-1NUL\s0 terminated. See the \*(L"\s-1EXAMPLES\*(R"\s0 section below.
506 The \s-1PEM\s0 reading functions will skip any extraneous content or \s-1PEM\s0 data of
508 (or multiple certificates) and a key in the \s-1PEM\s0 format in a single file.
520 A frequent cause of problems is attempting to use the \s-1PEM\s0 routines like
559 parameter. Internally, \fB\s-1PKCS5_SALT_LEN\s0\fR bytes of the salt are used
567 \&\fBEVP_BytesToKey()\fR is not utilized or needed, and \s-1NULL\s0 should be passed to
590 The \s-1PEM\s0 read routines in some versions of OpenSSL will not correctly reuse
608 The read routines return either a pointer to the structure read or \s-1NULL\s0
614 Although the \s-1PEM\s0 routines take several arguments in almost all applications
615 most of them are set to 0 or \s-1NULL.\s0
617 To read a certificate with a library context in \s-1PEM\s0 format from a \s-1BIO:\s0
629 Read a certificate in \s-1PEM\s0 format from a \s-1BIO:\s0
648 Write a certificate to a \s-1BIO:\s0
655 Write a private key (using traditional format) to a \s-1BIO\s0 using
656 triple \s-1DES\s0 encryption, the pass phrase is prompted for:
663 Write a private key (using PKCS#8 format) to a \s-1BIO\s0 using triple
664 \&\s-1DES\s0 encryption, using the pass phrase \*(L"hello\*(R":
672 Read a private key from a \s-1BIO\s0 using a pass phrase callback:
709 in OpenSSL 1.1.0; applications should use the \s-1PKCS7\s0 standard instead
736 in the file \s-1LICENSE\s0 in the source distribution or at