5 d2i_ACCESS_DESCRIPTION,
7 d2i_ASIdentifierChoice,
12 d2i_ASN1_GENERALIZEDTIME,
13 d2i_ASN1_GENERALSTRING,
18 d2i_ASN1_OCTET_STRING,
20 d2i_ASN1_PRINTABLESTRING,
21 d2i_ASN1_SEQUENCE_ANY,
27 d2i_ASN1_UNIVERSALSTRING,
30 d2i_ASN1_VISIBLESTRING,
32 d2i_AUTHORITY_INFO_ACCESS,
34 d2i_BASIC_CONSTRAINTS,
35 d2i_CERTIFICATEPOLICIES,
37 d2i_CMS_ReceiptRequest,
46 d2i_DSAPrivateKey_bio,
64 d2i_ESS_ISSUER_SERIAL,
66 d2i_EXTENDED_KEY_USAGE,
73 d2i_ISSUING_DIST_POINT,
74 d2i_NETSCAPE_CERT_SEQUENCE,
106 d2i_PKCS7_ENC_CONTENT,
108 d2i_PKCS7_ISSUER_AND_SERIAL,
109 d2i_PKCS7_RECIP_INFO,
111 d2i_PKCS7_SIGNER_INFO,
112 d2i_PKCS7_SIGN_ENVELOPE,
115 d2i_PKCS8_PRIV_KEY_INFO,
116 d2i_PKCS8_PRIV_KEY_INFO_bio,
117 d2i_PKCS8_PRIV_KEY_INFO_fp,
120 d2i_PKEY_USAGE_PERIOD,
123 d2i_PROXY_CERT_INFO_EXTENSION,
126 d2i_RSAPrivateKey_bio,
127 d2i_RSAPrivateKey_fp,
129 d2i_RSAPublicKey_bio,
142 d2i_TS_MSG_IMPRINT_bio,
143 d2i_TS_MSG_IMPRINT_fp,
177 i2d_ACCESS_DESCRIPTION,
179 i2d_ASIdentifierChoice,
184 i2d_ASN1_GENERALIZEDTIME,
185 i2d_ASN1_GENERALSTRING,
190 i2d_ASN1_OCTET_STRING,
192 i2d_ASN1_PRINTABLESTRING,
193 i2d_ASN1_SEQUENCE_ANY,
198 i2d_ASN1_UNIVERSALSTRING,
201 i2d_ASN1_VISIBLESTRING,
204 i2d_AUTHORITY_INFO_ACCESS,
206 i2d_BASIC_CONSTRAINTS,
207 i2d_CERTIFICATEPOLICIES,
209 i2d_CMS_ReceiptRequest,
218 i2d_DSAPrivateKey_bio,
219 i2d_DSAPrivateKey_fp,
229 i2d_ECPrivateKey_bio,
236 i2d_ESS_ISSUER_SERIAL,
237 i2d_ESS_SIGNING_CERT,
238 i2d_EXTENDED_KEY_USAGE,
243 i2d_IPAddressOrRange,
245 i2d_ISSUING_DIST_POINT,
246 i2d_NETSCAPE_CERT_SEQUENCE,
261 i2d_OCSP_REVOKEDINFO,
278 i2d_PKCS7_ENC_CONTENT,
280 i2d_PKCS7_ISSUER_AND_SERIAL,
282 i2d_PKCS7_RECIP_INFO,
284 i2d_PKCS7_SIGNER_INFO,
285 i2d_PKCS7_SIGN_ENVELOPE,
288 i2d_PKCS8PrivateKeyInfo_bio,
289 i2d_PKCS8PrivateKeyInfo_fp,
290 i2d_PKCS8_PRIV_KEY_INFO,
291 i2d_PKCS8_PRIV_KEY_INFO_bio,
292 i2d_PKCS8_PRIV_KEY_INFO_fp,
295 i2d_PKEY_USAGE_PERIOD,
298 i2d_PROXY_CERT_INFO_EXTENSION,
302 i2d_RSAPrivateKey_bio,
303 i2d_RSAPrivateKey_fp,
305 i2d_RSAPublicKey_bio,
318 i2d_TS_MSG_IMPRINT_bio,
319 i2d_TS_MSG_IMPRINT_fp,
353 - convert objects from/to ASN.1/DER representation
359 TYPE *d2i_TYPE(TYPE **a, unsigned char **pp, long length);
360 TYPE *d2i_TYPE_bio(BIO *bp, TYPE **a);
361 TYPE *d2i_TYPE_fp(FILE *fp, TYPE **a);
363 int i2d_TYPE(TYPE *a, unsigned char **pp);
364 int i2d_TYPE_fp(FILE *fp, TYPE *a);
365 int i2d_TYPE_bio(BIO *bp, TYPE *a);
369 In the description here, I<TYPE> is used a placeholder
370 for any of the OpenSSL datatypes, such as I<X509_CRL>.
372 These functions convert OpenSSL objects to and from their ASN.1/DER
373 encoding. Unlike the C structures which can have pointers to sub-objects
374 within, the DER is a serialized encoding, suitable for sending over the
375 network, writing to a file, and so on.
377 d2i_TYPE() attempts to decode B<len> bytes at B<*in>. If successful a
378 pointer to the B<TYPE> structure is returned and B<*in> is incremented to
379 the byte following the parsed data. If B<a> is not B<NULL> then a pointer
380 to the returned structure is also written to B<*a>. If an error occurred
381 then B<NULL> is returned.
383 On a successful return, if B<*a> is not B<NULL> then it is assumed that B<*a>
384 contains a valid B<TYPE> structure and an attempt is made to reuse it. This
385 "reuse" capability is present for historical compatibility but its use is
386 B<strongly discouraged> (see BUGS below, and the discussion in the RETURN
389 d2i_TYPE_bio() is similar to d2i_TYPE() except it attempts
390 to parse data from BIO B<bp>.
392 d2i_TYPE_fp() is similar to d2i_TYPE() except it attempts
393 to parse data from FILE pointer B<fp>.
395 i2d_TYPE() encodes the structure pointed to by B<a> into DER format.
396 If B<out> is not B<NULL>, it writes the DER encoded data to the buffer
397 at B<*out>, and increments it to point after the data just written.
398 If the return value is negative an error occurred, otherwise it
399 returns the length of the encoded data.
401 If B<*out> is B<NULL> memory will be allocated for a buffer and the encoded
402 data written to it. In this case B<*out> is not incremented and it points
403 to the start of the data just written.
405 i2d_TYPE_bio() is similar to i2d_TYPE() except it writes
406 the encoding of the structure B<a> to BIO B<bp> and it
407 returns 1 for success and 0 for failure.
409 i2d_TYPE_fp() is similar to i2d_TYPE() except it writes
410 the encoding of the structure B<a> to BIO B<bp> and it
411 returns 1 for success and 0 for failure.
413 These routines do not encrypt private keys and therefore offer no
414 security; use L<PEM_write_PrivateKey(3)> or similar for writing to files.
418 The letters B<i> and B<d> in B<i2d_TYPE> stand for
419 "internal" (that is, an internal C structure) and "DER" respectively.
420 So B<i2d_TYPE> converts from internal to DER.
422 The functions can also understand B<BER> forms.
424 The actual TYPE structure passed to i2d_TYPE() must be a valid
425 populated B<TYPE> structure -- it B<cannot> simply be fed with an
426 empty structure such as that returned by TYPE_new().
428 The encoded data is in binary form and may contain embedded zeroes.
429 Therefore any FILE pointers or BIOs should be opened in binary mode.
430 Functions such as strlen() will B<not> return the correct length
431 of the encoded structure.
433 The ways that B<*in> and B<*out> are incremented after the operation
434 can trap the unwary. See the B<WARNINGS> section for some common
436 The reason for this-auto increment behaviour is to reflect a typical
437 usage of ASN1 functions: after one structure is encoded or decoded
438 another will be processed after it.
440 The following points about the data types might be useful:
446 Represents an ASN1 OBJECT IDENTIFIER.
450 Represents a PKCS#3 DH parameters structure.
454 Represents a ANSI X9.42 DH parameters structure.
458 Represents a DSA public key using a B<SubjectPublicKeyInfo> structure.
460 =item B<DSAPublicKey, DSAPrivateKey>
462 Use a non-standard OpenSSL format and should be avoided; use B<DSA_PUBKEY>,
463 B<PEM_write_PrivateKey(3)>, or similar instead.
465 =item B<RSAPublicKey>
467 Represents a PKCS#1 RSA public key structure.
471 Represents an B<AlgorithmIdentifier> structure as used in IETF RFC 6960 and
476 Represents a B<Name> type as used for subject and issuer names in
477 IETF RFC 6960 and elsewhere.
481 Represents a PKCS#10 certificate request.
485 Represents the B<DigestInfo> structure defined in PKCS#1 and PKCS#7.
491 Allocate and encode the DER encoding of an X509 structure:
497 len = i2d_X509(x, &buf);
501 Attempt to decode a buffer:
504 unsigned char *buf, *p;
507 /* Set up buf and len to point to the input buffer. */
509 x = d2i_X509(NULL, &p, len);
513 Alternative technique:
516 unsigned char *buf, *p;
519 /* Set up buf and len to point to the input buffer. */
523 if (d2i_X509(&x, &p, len) == NULL)
528 Using a temporary variable is mandatory. A common
529 mistake is to attempt to use a buffer directly as follows:
534 len = i2d_X509(x, NULL);
535 buf = OPENSSL_malloc(len);
541 This code will result in B<buf> apparently containing garbage because
542 it was incremented after the call to point after the data just written.
543 Also B<buf> will no longer contain the pointer allocated by OPENSSL_malloc()
544 and the subsequent call to OPENSSL_free() is likely to crash.
546 Another trap to avoid is misuse of the B<a> argument to d2i_TYPE():
550 if (d2i_X509(&x, &p, len) == NULL)
553 This will probably crash somewhere in d2i_X509(). The reason for this
554 is that the variable B<x> is uninitialized and an attempt will be made to
555 interpret its (invalid) value as an B<X509> structure, typically causing
556 a segmentation violation. If B<x> is set to NULL first then this will not
561 In some versions of OpenSSL the "reuse" behaviour of d2i_TYPE() when
562 B<*px> is valid is broken and some parts of the reused structure may
563 persist if they are not present in the new one. As a result the use
564 of this "reuse" behaviour is strongly discouraged.
566 i2d_TYPE() will not return an error in many versions of OpenSSL,
567 if mandatory fields are not initialized due to a programming error
568 then the encoded structure may contain invalid data or omit the
569 fields entirely and will not be parsed by d2i_TYPE(). This may be
570 fixed in future so code should not assume that i2d_TYPE() will
573 Any function which encodes a structure (i2d_TYPE(),
574 i2d_TYPE() or i2d_TYPE()) may return a stale encoding if the
575 structure has been modified after deserialization or previous
576 serialization. This is because some objects cache the encoding for
581 d2i_TYPE(), d2i_TYPE_bio() and d2i_TYPE_fp() return a valid B<TYPE> structure
582 or B<NULL> if an error occurs. If the "reuse" capability has been used with
583 a valid structure being passed in via B<a>, then the object is not freed in
584 the event of error but may be in a potentially invalid or inconsistent state.
586 i2d_TYPE() returns the number of bytes successfully encoded or a negative
587 value if an error occurs.
589 i2d_TYPE_bio() and i2d_TYPE_fp() return 1 for success and 0 if an error
594 Copyright 1998-2016 The OpenSSL Project Authors. All Rights Reserved.
596 Licensed under the OpenSSL license (the "License"). You may not use
597 this file except in compliance with the License. You can obtain a copy
598 in the file LICENSE in the source distribution or at
599 L<https://www.openssl.org/source/license.html>.