summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_ATTRIBUTE_new.3
diff options
context:
space:
mode:
authorschwarze <>2016-12-22 16:05:22 +0000
committerschwarze <>2016-12-22 16:05:22 +0000
commitc0effee5bc1f5cdc6f4668d160e173746cbbf7de (patch)
treea214bad3e268c7c3de500b995d829ef4803ca1a0 /src/lib/libcrypto/man/X509_ATTRIBUTE_new.3
parent38633ba03a5091d9b9b3db1ecffb4f92a0043e1a (diff)
downloadopenbsd-c0effee5bc1f5cdc6f4668d160e173746cbbf7de.tar.gz
openbsd-c0effee5bc1f5cdc6f4668d160e173746cbbf7de.tar.bz2
openbsd-c0effee5bc1f5cdc6f4668d160e173746cbbf7de.zip
Write new manual pages PKCS12_new(3) and PKCS12_SAFEBAG_new(3) from
scratch. All these functions are listed in <openssl/pkcs12.h> and in OpenSSL doc/man3/X509_dup.pod. As usual, OpenSSL documentation specifies the wrong header file. Note that PKCS#12 documentation is still scanty at best. For example, out of 19 public functions handling PKCS12 objects, five are now documented, and this commit documents the first two out of 24 public functions handling PKCS12_SAFEBAG objects.
Diffstat (limited to 'src/lib/libcrypto/man/X509_ATTRIBUTE_new.3')
-rw-r--r--src/lib/libcrypto/man/X509_ATTRIBUTE_new.318
1 files changed, 13 insertions, 5 deletions
diff --git a/src/lib/libcrypto/man/X509_ATTRIBUTE_new.3 b/src/lib/libcrypto/man/X509_ATTRIBUTE_new.3
index 1410bd5c78..49aa238da7 100644
--- a/src/lib/libcrypto/man/X509_ATTRIBUTE_new.3
+++ b/src/lib/libcrypto/man/X509_ATTRIBUTE_new.3
@@ -1,4 +1,4 @@
1.\" $OpenBSD: X509_ATTRIBUTE_new.3,v 1.1 2016/12/17 14:51:09 schwarze Exp $ 1.\" $OpenBSD: X509_ATTRIBUTE_new.3,v 1.2 2016/12/22 16:05:22 schwarze Exp $
2.\" 2.\"
3.\" Copyright (c) 2016 Ingo Schwarze <schwarze@openbsd.org> 3.\" Copyright (c) 2016 Ingo Schwarze <schwarze@openbsd.org>
4.\" 4.\"
@@ -14,7 +14,7 @@
14.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF 14.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 15.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
16.\" 16.\"
17.Dd $Mdocdate: December 17 2016 $ 17.Dd $Mdocdate: December 22 2016 $
18.Dt X509_ATTRIBUTE_NEW 3 18.Dt X509_ATTRIBUTE_NEW 3
19.Os 19.Os
20.Sh NAME 20.Sh NAME
@@ -36,11 +36,15 @@ used to represent any kind of property of any kind of directory entry.
36In OpenSSL, very few objects use it directly, most notably the 36In OpenSSL, very few objects use it directly, most notably the
37.Vt X509_REQ_INFO 37.Vt X509_REQ_INFO
38object used for PKCS#10 certification requests described in 38object used for PKCS#10 certification requests described in
39.Xr X509_REQ_new 3 39.Xr X509_REQ_new 3 ,
40and the 40the
41.Vt PKCS8_PRIV_KEY_INFO 41.Vt PKCS8_PRIV_KEY_INFO
42object used for PKCS#8 private key information described in 42object used for PKCS#8 private key information described in
43.Xr PKCS8_PRIV_KEY_INFO_new 3 . 43.Xr PKCS8_PRIV_KEY_INFO_new 3 ,
44and the
45.Vt PKCS12_SAFEBAG
46container object described in
47.Xr PKCS12_SAFEBAG_new 3 .
44.Pp 48.Pp
45.Fn X509_ATTRIBUTE_new 49.Fn X509_ATTRIBUTE_new
46allocates and initializes an empty 50allocates and initializes an empty
@@ -57,6 +61,7 @@ object or
57.Dv NULL 61.Dv NULL
58if an error occurs. 62if an error occurs.
59.Sh SEE ALSO 63.Sh SEE ALSO
64.Xr PKCS12_SAFEBAG_new 3 ,
60.Xr PKCS8_PRIV_KEY_INFO_new 3 , 65.Xr PKCS8_PRIV_KEY_INFO_new 3 ,
61.Xr X509_EXTENSION_new 3 , 66.Xr X509_EXTENSION_new 3 ,
62.Xr X509_REQ_new 3 67.Xr X509_REQ_new 3
@@ -72,6 +77,9 @@ section 4.1: CertificationRequestInfo
72.It For the specific use in the context of private key information: 77.It For the specific use in the context of private key information:
73RFC 5208: Public-Key Cryptography Standards (PKCS) #8: 78RFC 5208: Public-Key Cryptography Standards (PKCS) #8:
74Private-Key Information Syntax Specification 79Private-Key Information Syntax Specification
80.It For the specific definition in the context of PFX:
81RFC 7292: PKCS #12: Personal Information Exchange Syntax,
82section 4.2: The SafeBag Type
75.El 83.El
76.Sh BUGS 84.Sh BUGS
77A data type designed to hold arbitrary data is an oxymoron. 85A data type designed to hold arbitrary data is an oxymoron.