summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/SXNET_new.3
diff options
context:
space:
mode:
authortb <>2023-04-25 18:48:32 +0000
committertb <>2023-04-25 18:48:32 +0000
commit326188c5fb0d0373a3ac0c57922ede3500c468c5 (patch)
tree45ac67a10ac935d385254aab211068743021c681 /src/lib/libcrypto/man/SXNET_new.3
parent6c3bca154d6d7f953f61e2c4bf065eb94e485ce7 (diff)
downloadopenbsd-326188c5fb0d0373a3ac0c57922ede3500c468c5.tar.gz
openbsd-326188c5fb0d0373a3ac0c57922ede3500c468c5.tar.bz2
openbsd-326188c5fb0d0373a3ac0c57922ede3500c468c5.zip
Remove SXNET
Unused and no authorative information was found online in 2016
Diffstat (limited to 'src/lib/libcrypto/man/SXNET_new.3')
-rw-r--r--src/lib/libcrypto/man/SXNET_new.3139
1 files changed, 0 insertions, 139 deletions
diff --git a/src/lib/libcrypto/man/SXNET_new.3 b/src/lib/libcrypto/man/SXNET_new.3
deleted file mode 100644
index 9a723be203..0000000000
--- a/src/lib/libcrypto/man/SXNET_new.3
+++ /dev/null
@@ -1,139 +0,0 @@
1.\" $OpenBSD: SXNET_new.3,v 1.3 2018/03/21 17:57:48 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: March 21 2018 $
18.Dt SXNET_NEW 3
19.Os
20.Sh NAME
21.Nm SXNET_new ,
22.Nm SXNET_free ,
23.Nm SXNETID_new ,
24.Nm SXNETID_free ,
25.Nm d2i_SXNET ,
26.Nm i2d_SXNET ,
27.Nm d2i_SXNETID ,
28.Nm i2d_SXNETID
29.Nd Thawte strong extranet X.509 extension
30.Sh SYNOPSIS
31.In openssl/x509v3.h
32.Ft SXNET *
33.Fn SXNET_new void
34.Ft void
35.Fn SXNET_free "SXNET *sxnet"
36.Ft SXNETID *
37.Fn SXNETID_new void
38.Ft void
39.Fn SXNETID_free "SXNETID *sxnetid"
40.Ft SXNET *
41.Fo d2i_SXNET
42.Fa "SXNET **val_out"
43.Fa "const unsigned char **der_in"
44.Fa "long length"
45.Fc
46.Ft int
47.Fo i2d_SXNET
48.Fa "SXNET *val_in"
49.Fa "unsigned char **der_out"
50.Fc
51.Ft SXNETID *
52.Fo d2i_SXNETID
53.Fa "SXNETID **val_out"
54.Fa "const unsigned char **der_in"
55.Fa "long length"
56.Fc
57.Ft int
58.Fo i2d_SXNETID
59.Fa "SXNETID *val_in"
60.Fa "unsigned char **der_out"
61.Fc
62.Sh DESCRIPTION
63.Fn SXNET_new
64allocates and initializes an empty
65.Vt SXNET
66object representing a non-standard proprietary Thawte strong extranet
67X.509 extension.
68.Fn SXNET_free
69frees
70.Fa sxnet .
71.Pp
72.Fn SXNETID_new
73allocates and initializes an empty
74.Vt SXNETID
75object.
76It is used inside
77.Vt SXNET .
78.Fn SXNETID_free
79frees
80.Fa sxnetid .
81.Pp
82The remaining functions decode and encode these objects
83using DER format.
84For details about the semantics, examples, caveats, and bugs, see
85.Xr ASN1_item_d2i 3 .
86.Sh RETURN VALUES
87.Fn SXNET_new
88and
89.Fn d2i_SXNET
90return an
91.Vt SXNET
92object or
93.Dv NULL
94if an error occurs.
95.Pp
96.Fn SXNETID_new
97and
98.Fn d2i_SXNETID
99return an
100.Vt SXNETID
101object or
102.Dv NULL
103if an error occurs.
104.Pp
105.Fn i2d_SXNET
106and
107.Fn i2d_SXNETID
108return the number of bytes successfully encoded or a negative value
109if an error occurs.
110.Sh SEE ALSO
111.Xr X509_EXTENSION_new 3 ,
112.Xr X509_new 3
113.Rs
114.%A M. Shuttleworth
115.%R The Strong Extranet: real-world personal certification
116.%Q Thawte Consulting
117.%C South Africa
118.%D 1998
119.Re
120.Sh HISTORY
121These functions first appeared in OpenSSL 0.9.3
122and have been available since
123.Ox 2.6 .
124.Sh BUGS
125This manual page does not explain what the extension actually does
126because no authoritative information was found online so far.
127.Pp
128The only hint was found in an ancient white paper "Securing IBM
129Applications with Public Key Infrastructure" on the IBM website,
130dated June 13, 2001: "Thawte also has a technology called Strong
131Extranet that allows institutions to encode customer information
132in the extensions to their customer's certificates.
133Because multiple institutions can add information, the user needs
134only one certificate, making renewal and revocation simpler, although
135the issue of modifying an extension to an existing certificate is
136not addressed."
137.Pp
138It is unclear whether that explanation is accurate, but in any case,
139it is not very specific.