xref: /openbsd/lib/libcrypto/man/X509_SIG_new.3 (revision 5bcdf354)
1*5bcdf354Sschwarze.\"	$OpenBSD: X509_SIG_new.3,v 1.5 2021/10/27 11:24:47 schwarze Exp $
2d2cf0bc9Sschwarze.\"
3d2cf0bc9Sschwarze.\" Copyright (c) 2016 Ingo Schwarze <schwarze@openbsd.org>
4d2cf0bc9Sschwarze.\"
5d2cf0bc9Sschwarze.\" Permission to use, copy, modify, and distribute this software for any
6d2cf0bc9Sschwarze.\" purpose with or without fee is hereby granted, provided that the above
7d2cf0bc9Sschwarze.\" copyright notice and this permission notice appear in all copies.
8d2cf0bc9Sschwarze.\"
9d2cf0bc9Sschwarze.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
10d2cf0bc9Sschwarze.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
11d2cf0bc9Sschwarze.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
12d2cf0bc9Sschwarze.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
13d2cf0bc9Sschwarze.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14d2cf0bc9Sschwarze.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15d2cf0bc9Sschwarze.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
16d2cf0bc9Sschwarze.\"
17*5bcdf354Sschwarze.Dd $Mdocdate: October 27 2021 $
18d2cf0bc9Sschwarze.Dt X509_SIG_NEW 3
19d2cf0bc9Sschwarze.Os
20d2cf0bc9Sschwarze.Sh NAME
21d2cf0bc9Sschwarze.Nm X509_SIG_new ,
22d2cf0bc9Sschwarze.Nm X509_SIG_free
23d2cf0bc9Sschwarze.Nd PKCS#7 digest information
24d2cf0bc9Sschwarze.Sh SYNOPSIS
25d2cf0bc9Sschwarze.In openssl/x509.h
26d2cf0bc9Sschwarze.Ft X509_SIG *
27d2cf0bc9Sschwarze.Fn X509_SIG_new void
28d2cf0bc9Sschwarze.Ft void
29d2cf0bc9Sschwarze.Fn X509_SIG_free "X509_SIG *sig"
30d2cf0bc9Sschwarze.Sh DESCRIPTION
31d2cf0bc9Sschwarze.Fn X509_SIG_new
32d2cf0bc9Sschwarzeallocates and initializes an empty
33d2cf0bc9Sschwarze.Vt X509_SIG
3456bc162bSschwarzeobject, representing an ASN.1
3556bc162bSschwarze.Vt DigestInfo
3656bc162bSschwarzestructure defined in RFC 2315 section 9.4
3756bc162bSschwarzeand equivalently in RFC 8017 section 9.2.
38d2cf0bc9SschwarzeIt can hold a message digest together with information about
39d2cf0bc9Sschwarzethe algorithm used.
40d2cf0bc9Sschwarze.Pp
41d2cf0bc9Sschwarze.Fn X509_SIG_free
42d2cf0bc9Sschwarzefrees
43d2cf0bc9Sschwarze.Fa sig .
44d2cf0bc9Sschwarze.Sh RETURN VALUES
45d2cf0bc9Sschwarze.Fn X509_SIG_new
46d2cf0bc9Sschwarzereturns the new
47d2cf0bc9Sschwarze.Vt X509_SIG
48d2cf0bc9Sschwarzeobject or
49d2cf0bc9Sschwarze.Dv NULL
50d2cf0bc9Sschwarzeif an error occurs.
51d2cf0bc9Sschwarze.Sh SEE ALSO
52d2cf0bc9Sschwarze.Xr d2i_X509_SIG 3 ,
53d2cf0bc9Sschwarze.Xr PEM_read_PKCS8 3 ,
54d2cf0bc9Sschwarze.Xr RSA_sign 3 ,
55*5bcdf354Sschwarze.Xr X509_new 3 ,
56*5bcdf354Sschwarze.Xr X509_SIG_get0 3
57d2cf0bc9Sschwarze.Sh STANDARDS
58d2cf0bc9SschwarzeRFC 2315: PKCS #7: Cryptographic Message Syntax,
59d2cf0bc9Sschwarzesection 9: Signed-data content type
60d2cf0bc9Sschwarze.Pp
61d2cf0bc9SschwarzeRFC 8017: PKCS #1: RSA Cryptography Specifications,
62d2cf0bc9Sschwarzesection 9: Encoding Methods for Signatures
63d9d184f2Sschwarze.Sh HISTORY
64d9d184f2Sschwarze.Fn X509_SIG_new
65d9d184f2Sschwarzeand
66d9d184f2Sschwarze.Fn X509_SIG_free
6710e00d17Sschwarzeappeared in SSLeay 0.4 or earlier and have been available since
68d9d184f2Sschwarze.Ox 2.4 .
69