diff options
| author | cvs2svn <admin@example.com> | 2021-08-18 16:06:57 +0000 |
|---|---|---|
| committer | cvs2svn <admin@example.com> | 2021-08-18 16:06:57 +0000 |
| commit | d56c8fa8260d226f98b26f017b45b9c2b135f38d (patch) | |
| tree | 348178b41617813cc93787187984a734ef8379ca /src/lib/libcrypto/man/X509_ATTRIBUTE_new.3 | |
| parent | 18b9c1bcab7c37d8c5bd05b8e0d14d0c59d96650 (diff) | |
| download | openbsd-tb_20210818.tar.gz openbsd-tb_20210818.tar.bz2 openbsd-tb_20210818.zip | |
This commit was manufactured by cvs2git to create tag 'tb_20210818'.tb_20210818
Diffstat (limited to 'src/lib/libcrypto/man/X509_ATTRIBUTE_new.3')
| -rw-r--r-- | src/lib/libcrypto/man/X509_ATTRIBUTE_new.3 | 122 |
1 files changed, 0 insertions, 122 deletions
diff --git a/src/lib/libcrypto/man/X509_ATTRIBUTE_new.3 b/src/lib/libcrypto/man/X509_ATTRIBUTE_new.3 deleted file mode 100644 index 66779d637b..0000000000 --- a/src/lib/libcrypto/man/X509_ATTRIBUTE_new.3 +++ /dev/null | |||
| @@ -1,122 +0,0 @@ | |||
| 1 | .\" $OpenBSD: X509_ATTRIBUTE_new.3,v 1.8 2020/06/04 10:24:27 schwarze Exp $ | ||
| 2 | .\" | ||
| 3 | .\" Copyright (c) 2016 Ingo Schwarze <schwarze@openbsd.org> | ||
| 4 | .\" | ||
| 5 | .\" Permission to use, copy, modify, and distribute this software for any | ||
| 6 | .\" purpose with or without fee is hereby granted, provided that the above | ||
| 7 | .\" copyright notice and this permission notice appear in all copies. | ||
| 8 | .\" | ||
| 9 | .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES | ||
| 10 | .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF | ||
| 11 | .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR | ||
| 12 | .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES | ||
| 13 | .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN | ||
| 14 | .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF | ||
| 15 | .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. | ||
| 16 | .\" | ||
| 17 | .Dd $Mdocdate: June 4 2020 $ | ||
| 18 | .Dt X509_ATTRIBUTE_NEW 3 | ||
| 19 | .Os | ||
| 20 | .Sh NAME | ||
| 21 | .Nm X509_ATTRIBUTE_new , | ||
| 22 | .Nm X509_ATTRIBUTE_free | ||
| 23 | .\" In the following line, "X.501" and "Attribute" are not typos. | ||
| 24 | .\" The "Attribute" type is defined in X.501, not in X.509. | ||
| 25 | .\" The type in called "Attribute" with capital "A", not "attribute". | ||
| 26 | .Nd generic X.501 Attribute | ||
| 27 | .Sh SYNOPSIS | ||
| 28 | .In openssl/x509.h | ||
| 29 | .Ft X509_ATTRIBUTE * | ||
| 30 | .Fn X509_ATTRIBUTE_new void | ||
| 31 | .Ft void | ||
| 32 | .Fn X509_ATTRIBUTE_free "X509_ATTRIBUTE *attr" | ||
| 33 | .Sh DESCRIPTION | ||
| 34 | In the X.501 standard, an | ||
| 35 | .Vt Attribute | ||
| 36 | is the fundamental ASN.1 data type used to represent any kind of | ||
| 37 | property of any kind of directory entry. | ||
| 38 | In OpenSSL, very few objects use it directly, most notably the | ||
| 39 | .Vt X509_REQ_INFO | ||
| 40 | object used for PKCS#10 certification requests described in | ||
| 41 | .Xr X509_REQ_new 3 , | ||
| 42 | the | ||
| 43 | .Vt PKCS8_PRIV_KEY_INFO | ||
| 44 | object used for PKCS#8 private key information described in | ||
| 45 | .Xr PKCS8_PRIV_KEY_INFO_new 3 , | ||
| 46 | and the | ||
| 47 | .Vt PKCS12_SAFEBAG | ||
| 48 | container object described in | ||
| 49 | .Xr PKCS12_SAFEBAG_new 3 . | ||
| 50 | .Pp | ||
| 51 | .Fn X509_ATTRIBUTE_new | ||
| 52 | allocates and initializes an empty | ||
| 53 | .Vt X509_ATTRIBUTE | ||
| 54 | object. | ||
| 55 | .Fn X509_ATTRIBUTE_free | ||
| 56 | frees | ||
| 57 | .Fa attr . | ||
| 58 | .Sh RETURN VALUES | ||
| 59 | .Fn X509_ATTRIBUTE_new | ||
| 60 | returns the new | ||
| 61 | .Vt X509_ATTRIBUTE | ||
| 62 | object or | ||
| 63 | .Dv NULL | ||
| 64 | if an error occurs. | ||
| 65 | .Sh SEE ALSO | ||
| 66 | .Xr d2i_X509_ATTRIBUTE 3 , | ||
| 67 | .Xr PKCS12_SAFEBAG_new 3 , | ||
| 68 | .Xr PKCS7_add_attribute 3 , | ||
| 69 | .Xr PKCS8_PRIV_KEY_INFO_new 3 , | ||
| 70 | .Xr X509_EXTENSION_new 3 , | ||
| 71 | .Xr X509_new 3 , | ||
| 72 | .Xr X509_REQ_new 3 | ||
| 73 | .Sh STANDARDS | ||
| 74 | .Bl -ohang | ||
| 75 | .It Xo | ||
| 76 | For the general definition of the | ||
| 77 | .Vt Attribute | ||
| 78 | data type: | ||
| 79 | .Xc | ||
| 80 | ITU-T Recommendation X.501, also known as ISO/IEC 9594-2: | ||
| 81 | Information Technology \(en Open Systems Interconnection \(en | ||
| 82 | The Directory: Models, section 8.2: Overall structure | ||
| 83 | .It For the specific definition in the context of certification requests: | ||
| 84 | RFC 2986: PKCS #10: Certification Request Syntax Specification, | ||
| 85 | section 4.1: CertificationRequestInfo | ||
| 86 | .It For the specific use in the context of private key information: | ||
| 87 | RFC 5208: Public-Key Cryptography Standards (PKCS) #8: | ||
| 88 | Private-Key Information Syntax Specification | ||
| 89 | .It For the specific definition in the context of PFX: | ||
| 90 | RFC 7292: PKCS #12: Personal Information Exchange Syntax, | ||
| 91 | section 4.2: The SafeBag Type | ||
| 92 | .El | ||
| 93 | .Sh HISTORY | ||
| 94 | .Fn X509_ATTRIBUTE_new | ||
| 95 | and | ||
| 96 | .Fn X509_ATTRIBUTE_free | ||
| 97 | first appeared in SSLeay 0.5.1 and have been available since | ||
| 98 | .Ox 2.4 . | ||
| 99 | .Sh BUGS | ||
| 100 | A data type designed to hold arbitrary data is an oxymoron. | ||
| 101 | .Pp | ||
| 102 | While it may occasionally be useful for abstract syntax specification | ||
| 103 | or for generic container objects, using it for the representation | ||
| 104 | of specific data in a specific data structure feels like dubious | ||
| 105 | design. | ||
| 106 | .Pp | ||
| 107 | Having two distinct data types to hold arbitrary data \(en | ||
| 108 | in this case, | ||
| 109 | .Vt X509_ATTRIBUTE | ||
| 110 | on the X.501 language level and | ||
| 111 | .Vt X509_EXTENSION | ||
| 112 | as described in | ||
| 113 | .Xr X509_EXTENSION_new 3 | ||
| 114 | on the X.509 language level \(en feels even more questionable, | ||
| 115 | in particular considering that Attributes in certification requests | ||
| 116 | can be used to ask for Extensions in certificates. | ||
| 117 | .Pp | ||
| 118 | At the very least, the direct use of the low-level generic | ||
| 119 | .Vt X509_ATTRIBUTE | ||
| 120 | type in specific data types like certification requests or private | ||
| 121 | key information looks like a layering violation and appears to put | ||
| 122 | type safety into jeopardy. | ||
