diff options
| author | jim <> | 2014-05-04 21:46:36 +0000 |
|---|---|---|
| committer | jim <> | 2014-05-04 21:46:36 +0000 |
| commit | 94b4f752322026bbd9765e2b8084db237af47cd9 (patch) | |
| tree | a8892de8fd6e54fc93e929516a1ed1c754ef77fd /src/lib/libcrypto/doc/PEM_read_bio_PrivateKey.pod | |
| parent | c5c3edda5f74a18c2b4f5fd26c59daea4e6722b9 (diff) | |
| download | openbsd-94b4f752322026bbd9765e2b8084db237af47cd9.tar.gz openbsd-94b4f752322026bbd9765e2b8084db237af47cd9.tar.bz2 openbsd-94b4f752322026bbd9765e2b8084db237af47cd9.zip | |
Remove trailing whitespace.
fine jmc@
Diffstat (limited to 'src/lib/libcrypto/doc/PEM_read_bio_PrivateKey.pod')
| -rw-r--r-- | src/lib/libcrypto/doc/PEM_read_bio_PrivateKey.pod | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/lib/libcrypto/doc/PEM_read_bio_PrivateKey.pod b/src/lib/libcrypto/doc/PEM_read_bio_PrivateKey.pod index 54414a3f6f..e196bf1498 100644 --- a/src/lib/libcrypto/doc/PEM_read_bio_PrivateKey.pod +++ b/src/lib/libcrypto/doc/PEM_read_bio_PrivateKey.pod | |||
| @@ -250,7 +250,7 @@ structure. They will also process a trusted X509 certificate but | |||
| 250 | any trust settings are discarded. | 250 | any trust settings are discarded. |
| 251 | 251 | ||
| 252 | The B<X509_AUX> functions process a trusted X509 certificate using | 252 | The B<X509_AUX> functions process a trusted X509 certificate using |
| 253 | an X509 structure. | 253 | an X509 structure. |
| 254 | 254 | ||
| 255 | The B<X509_REQ> and B<X509_REQ_NEW> functions process a PKCS#10 | 255 | The B<X509_REQ> and B<X509_REQ_NEW> functions process a PKCS#10 |
| 256 | certificate request using an X509_REQ structure. The B<X509_REQ> | 256 | certificate request using an X509_REQ structure. The B<X509_REQ> |
| @@ -435,7 +435,7 @@ which is an uninitialised pointer. | |||
| 435 | 435 | ||
| 436 | This old B<PrivateKey> routines use a non standard technique for encryption. | 436 | This old B<PrivateKey> routines use a non standard technique for encryption. |
| 437 | 437 | ||
| 438 | The private key (or other data) takes the following form: | 438 | The private key (or other data) takes the following form: |
| 439 | 439 | ||
| 440 | -----BEGIN RSA PRIVATE KEY----- | 440 | -----BEGIN RSA PRIVATE KEY----- |
| 441 | Proc-Type: 4,ENCRYPTED | 441 | Proc-Type: 4,ENCRYPTED |
| @@ -461,7 +461,7 @@ an existing structure. Therefore the following: | |||
| 461 | 461 | ||
| 462 | PEM_read_bio_X509(bp, &x, 0, NULL); | 462 | PEM_read_bio_X509(bp, &x, 0, NULL); |
| 463 | 463 | ||
| 464 | where B<x> already contains a valid certificate, may not work, whereas: | 464 | where B<x> already contains a valid certificate, may not work, whereas: |
| 465 | 465 | ||
| 466 | X509_free(x); | 466 | X509_free(x); |
| 467 | x = PEM_read_bio_X509(bp, NULL, 0, NULL); | 467 | x = PEM_read_bio_X509(bp, NULL, 0, NULL); |
