1 .\" $OpenBSD: SXNET_new.3,v 1.2 2016/12/28 20:36:33 schwarze Exp $
3 .\" Copyright (c) 2016 Ingo Schwarze <schwarze@openbsd.org>
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.
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.
17 .Dd $Mdocdate: December 28 2016 $
29 .Nd Thawte strong extranet X.509 extension
35 .Fn SXNET_free "SXNET *sxnet"
39 .Fn SXNETID_free "SXNETID *sxnetid"
43 .Fa "const unsigned char **der_in"
49 .Fa "unsigned char **der_out"
53 .Fa "SXNETID **val_out"
54 .Fa "const unsigned char **der_in"
60 .Fa "unsigned char **der_out"
64 allocates and initializes an empty
66 object representing a non-standard proprietary Thawte strong extranet
73 allocates and initializes an empty
82 The remaining functions decode and encode these objects
84 For details about the semantics, examples, caveats, and bugs, see
108 return the number of bytes successfully encoded or a negative value
111 .Xr X509_EXTENSION_new 3 ,
115 .%R The Strong Extranet: real-world personal certification
116 .%Q Thawte Consulting
121 This manual page does not explain what the extension actually does
122 because no authoritative information was found online so far.
124 The only hint was found in an ancient white paper "Securing IBM
125 Applications with Public Key Infrastructure" on the IBM website,
126 dated June 13, 2001: "Thawte also has a technology called Strong
127 Extranet that allows institutions to encode customer information
128 in the extensions to their customer's certificates.
129 Because multiple institutions can add information, the user needs
130 only one certificate, making renewal and revocation simpler, although
131 the issue of modifying an extension to an existing certificate is
134 It is unclear whether that explanation is accurate, but in any case,
135 it is not very specific.