| /netbsd-src/crypto/external/bsd/heimdal/dist/lib/asn1/ |
| H A D | asn1_err.et | 10 error_code BAD_TIMEFORMAT, "ASN.1 failed call to system time library"
11 error_code MISSING_FIELD, "ASN.1 structure is missing a required field"
12 error_code MISPLACED_FIELD, "ASN.1 unexpected field number"
13 error_code TYPE_MISMATCH, "ASN.1 type numbers are inconsistent"
14 error_code OVERFLOW, "ASN.1 value too large"
15 error_code OVERRUN, "ASN.1 encoding ended unexpectedly"
16 error_code BAD_ID, "ASN.1 identifier doesn't match expected value"
17 error_code BAD_LENGTH, "ASN.1 length doesn't match expected value"
18 error_code BAD_FORMAT, "ASN.1 badly-formatted encoding"
19 error_code PARSE_ERROR, "ASN.1 parse error"
[all …]
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/po/heim_com_err1859794432/ |
| H A D | heim_com_err1859794432.pot | 20 msgid "ASN.1 failed call to system time library"
25 msgid "ASN.1 structure is missing a required field"
30 msgid "ASN.1 unexpected field number"
35 msgid "ASN.1 type numbers are inconsistent"
40 msgid "ASN.1 value too large"
45 msgid "ASN.1 encoding ended unexpectedly"
50 msgid "ASN.1 identifier doesn't match expected value"
55 msgid "ASN.1 length doesn't match expected value"
60 msgid "ASN.1 badly-formatted encoding"
65 msgid "ASN.1 parse error"
[all …]
|
| /netbsd-src/external/bsd/unbound/dist/contrib/ |
| H A D | aaaa-filter-iterator.patch | 28 + * ASN: Lookup A records from rrset cache.
45 + log_rrset_key(VERB_ALGO, "ASN-AAAA-filter: found A record",
60 + int found_a_record = 0; /* ASN: do we have a A record? */
68 + /* ASN: Locate any A record we can find */
73 + /* ASN: End of added code */
82 + /* ASN: For AAAA records only... */
84 + /* ASN: If this is not a AAAA query, then remove AAAA
90 + remove_rrset("ASN-AAAA-filter: removing AAAA "
94 + log_nametypeclass(VERB_ALGO, "ASN-AAAA-filter: "
98 + /* ASN: End of added code */
[all …]
|
| /netbsd-src/external/bsd/openldap/dist/doc/rfc/ |
| H A D | rfc3687.txt | 129 Syntax Notation One (ASN.1) [13] type definitions. ASN.1 type
136 syntaxes and the X.500 ASN.1 types. To a large extent, the data
138 described by ASN.1 types. This formal description can be exploited
152 using ASN.1 type notation. All of the type notations defined in
176 of attribute values of any syntax described by an ASN.1 type
184 the LDAP and X.500 binary encoding (and possibly other ASN.1
187 simply writing down an ASN.1 type definition for the syntax. These
188 implicit definitions are also automatically extended if the ASN.1
190 ASN.1 type definition, the various encodings and the component
193 from ASN.1 type definitions.
[all …]
|
| H A D | rfc3727.txt | 12 ASN.1 Module Definition for the
32 (ASN.1) definitions of the component matching rules into an
33 appropriately identified ASN.1 module so that other specifications
35 their own ASN.1 modules.
49 Notation One (ASN.1) [ASN1] definitions of RFC 3687 into an
50 appropriately identified ASN.1 module so that other specifications
51 may reference these definitions from within their own ASN.1 modules.
69 -- this ASN.1 module is part of RFC 3727; see the RFC itself
128 The InformationFramework ASN.1 module from which the MATCHING-RULE
138 This document collects together the ASN.1 definitions of the
[all …]
|
| H A D | rfc2926.txt | 39 If arbitrary ASN.1 types occur in the schema, then the mapping is
85 4.2 Mapping ASN.1 Types to SLP Types .......................... 17
92 4.3 Example ASN.1 Schema ...................................... 19
145 RFC 2252 [8]. This syntax is a subset of the ASN.1/BER described in
148 consistent mapping of ASN.1 based schemas to be translated in the SLP
413 SLP Type ASN.1 Type LDAP Type
478 ASN.1 has no concept of keyword attributes. Keyword attributes are
479 translated into a "May" clause in the ASN.1 class definition for the
515 clause in the ASN.1 definition class definition for the service type.
520 ASN.1 does not have a mechanism to indicate that the values of an
[all …]
|
| H A D | rfc4517.txt | 251 [ASN.1] represented in the dotted-decimal format (short descriptive
324 This syntax corresponds to the AttributeTypeDescription ASN.1 type
352 This syntax corresponds to the BIT STRING ASN.1 type from [ASN.1].
366 This syntax corresponds to the BOOLEAN ASN.1 type from [ASN.1].
388 This syntax corresponds to the following ASN.1 type from [X.520]:
420 This syntax corresponds to the following ASN.1 type from [X.520]:
471 This syntax corresponds to the DirectoryString parameterized ASN.1
474 The DirectoryString ASN.1 type allows a choice between the
475 TeletexString, PrintableString, or UniversalString ASN.1 types from
476 [ASN.1]. However, note that the chosen alternative is not indicated
[all …]
|
| H A D | rfc4521.txt | 86 4. Extending the LDAP ASN.1 Definition .............................9
90 4.4. General ASN.1 Extensibility ...............................10
144 Syntax Notation - One (ASN.1) [X.680] definition to be made. This
147 extension of the protocol's ASN.1 definition.
245 Numerous elements of LDAP are described using ASN.1 [X.680] and are
251 responseValue fields) described by ASN.1 and encoded using BER be
472 4. Extending the LDAP ASN.1 Definition
474 LDAP allows limited extension [Protocol, Section 4] of the LDAP ASN.1
529 4.4. General ASN.1 Extensibility
534 extensibility is implied where it is allowed per ASN.1 (i.e.,
[all …]
|
| /netbsd-src/crypto/external/bsd/openssl/dist/doc/man3/ |
| H A D | ASN1_TYPE_get.pod | 24 B<ASN1_TYPE> structure can contain any ASN.1 type or constructed type
25 such as a SEQUENCE: it is effectively equivalent to the ASN.1 ANY type.
35 ASN1_TYPE_cmp() compares ASN.1 types I<a> and I<b> and returns 0 if
39 I<t> using the ASN.1 structure I<it>. If successful it returns a pointer
40 to the ASN.1 structure corresponding to I<it> which must be freed by the
43 ASN1_TYPE_pack_sequence() attempts to encode the ASN.1 structure I<s>
61 B<ASN1_STRING> contains the entire ASN.1 encoding verbatim (including tag and
86 ASN1_TYPE_unpack_sequence() returns a pointer to an ASN.1 structure or
|
| H A D | ASN1_item_d2i_bio.pod | 7 - decode and encode DER-encoded ASN.1 structures
32 I<len> which must be a DER-encoded ASN.1 structure, using the ASN.1 template
46 which must be a DER-encoded ASN.1 structure, using the ASN.1 template I<it>
65 ASN1_item_i2d_mem_bio() encodes the given ASN.1 value I<val>
66 using the ASN.1 template I<it> and returns the result in a memory BIO.
|
| H A D | EVP_PKEY_asn1_get_count.pod | 10 - enumerate public key ASN.1 methods
29 ASN.1 methods available: it includes standard methods and any methods
32 EVP_PKEY_asn1_get0() returns the public key ASN.1 method B<idx>.
51 associated with the public key ASN.1 method B<*ameth>.
|
| H A D | PKCS12_item_decrypt_d2i.pod | 35 string containing an ASN.1 encoded object using the algorithm I<algor> and
39 PKCS12_item_i2d_encrypt() and PKCS12_item_i2d_encrypt_ex() encrypt an ASN.1
53 data as an ASN.1 Octet String or NULL if an error occurred.
|
| H A D | ASN1_item_sign.pod | 43 I<data>, the ASN.1 structure I<it>, private key I<pkey> and message digest I<md>.
45 converting it to der format using the ASN.1 structure I<it>.
52 Examples of valid values that can be used by the ASN.1 structure I<it> are
71 converting it to der format using the ASN.1 structure I<it>.
166 * it contains the mapping between ASN.1 data and an object MySignInfoObject
|
| H A D | ASN1_aux_cb.pod | 6 - ASN.1 auxiliary data
44 ASN.1 data structures can be associated with an B<ASN1_AUX> object to supply
45 additional information about the ASN.1 structure. An B<ASN1_AUX> structure is
46 associated with the structure during the definition of the ASN.1 template. For
48 ASN.1 template definition macros that supply auxiliary information such as
|
| H A D | OSSL_ALGORITHM.pod | 58 L<PKCS#1 RFC's ASN.1 module|https://www.rfc-editor.org/rfc/rfc8017#appendix-C>
105 Providers may find the need to register ASN.1 OIDs for algorithms using
113 Most of the time, registering ASN.1 OIDs like this shouldn't be necessary,
|
| /netbsd-src/crypto/external/bsd/openssl.old/dist/doc/man3/ |
| H A D | ASN1_TYPE_get.pod | 24 ASN1_TYPE structure can contain any ASN.1 type or constructed type
25 such as a SEQUENCE: it is effectively equivalent to the ASN.1 ANY type.
35 ASN1_TYPE_cmp() compares ASN.1 types B<a> and B<b> and returns 0 if
39 B<t> using the ASN.1 structure B<it>. If successful it returns a pointer
40 to the ASN.1 structure corresponding to B<it> which must be freed by the
43 ASN1_TYPE_pack_sequence() attempts to encode the ASN.1 structure B<s>
60 ASN1_STRING contains the entire ASN.1 encoding verbatim (including tag and
85 ASN1_TYPE_unpack_sequence() returns a pointer to an ASN.1 structure or
|
| H A D | EVP_PKEY_asn1_get_count.pod | 10 - enumerate public key ASN.1 methods
29 ASN.1 methods available: it includes standard methods and any methods
32 EVP_PKEY_asn1_get0() returns the public key ASN.1 method B<idx>.
51 associated with the public key ASN.1 method B<*ameth>.
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/doc/ |
| H A D | layman.asc | 1 A Layman's Guide to a Subset of ASN.1, BER, and DER
22 subset of OSI's Abstract Syntax Notation One (ASN.1), Basic
57 OSI's method of specifying abstract objects is called ASN.1
61 defined in X.209). ASN.1 is a flexible notation that allows
66 each ASN.1 type as a string of eight-bit octets. There is
70 encoding to each ASN.1 value.
72 The purpose of this note is to describe a subset of ASN.1,
76 overview of ASN.1, BER, and DER and an abridged list of
77 ASN.1 types and their BER and DER encodings. Sections 2-4
78 give an overview of ASN.1, BER, and DER, in that order.
[all …]
|
| /netbsd-src/external/bsd/openldap/dist/contrib/slapd-modules/comp_match/ |
| H A D | README | 25 GSER and BER decoder library of each primitive ASN.1 type.
26 They use component representation to store ASN.1 values.
34 An mapping table from ASN.1 types to corresponding Syntaxes,
60 C) How to add a new ASN.1 syntax
70 2) using eSNACC, compile your ASN.1 specifications and
95 BER. Currently primitive ASN.1 types, DN, and RDN
|
| /netbsd-src/crypto/external/bsd/openssl.old/dist/doc/man1/ |
| H A D | asn1parse.pod | 6 asn1parse - ASN.1 parsing tool
30 The B<asn1parse> command is a diagnostic utility that can parse ASN.1
31 structures. It can also be used to extract data from ASN.1 formatted data.
87 Parse the contents octets of the ASN.1 object starting at B<offset>. This
110 print out the fields of any supported ASN.1 structure if the type is known.
143 Some knowledge of the ASN.1 structure is needed to interpret the output.
200 ASN.1 types is not well handled (if at all).
|
| /netbsd-src/crypto/external/bsd/openssl/dist/doc/man1/ |
| H A D | openssl-asn1parse.pod.in | 6 openssl-asn1parse - ASN.1 parsing command
30 This command is a diagnostic utility that can parse ASN.1 structures.
31 It can also be used to extract data from ASN.1 formatted data.
87 Parse the contents octets of the ASN.1 object starting at B<offset>. This
110 used to print out the fields of any supported ASN.1 structure if the type is
144 Some knowledge of the ASN.1 structure is needed to interpret the output.
204 ASN.1 types is not well handled (if at all).
|
| /netbsd-src/crypto/external/bsd/openssl/dist/doc/internal/man3/ |
| H A D | ossl_DER_w_begin_sequence.pod | 18 i.e. the ASN.1 SEQUENCE, SET and CHOICE specifications. They all come
22 When using these, special care must be taken to ensure that the ASN.1 tag
|
| /netbsd-src/crypto/external/bsd/openssl/dist/doc/man7/ |
| H A D | openssl-glossary.pod | 21 =item ASN.1, ASN1
23 ASN.1 ("Abstract Syntax Notation One") is a notation for describing abstract
57 DER is a binary encoding of data, structured according to an ASN.1
163 PKCS#8 is a specification of ASN.1 structures that OpenSSL uses for storing
209 SubjectPublicKeyInfo is an ASN.1 structure that OpenSSL uses for storing and
|
| /netbsd-src/crypto/external/bsd/openssl/dist/doc/internal/man7/ |
| H A D | DERlib.pod | 43 which is defined like this in ASN.1 terms:
58 As an example of the use of I<tag>, an ASN.1 element like this:
99 The value we want to encode, written in ASN.1 syntax:
|
| /netbsd-src/external/bsd/openldap/dist/doc/drafts/ |
| H A D | draft-sermersheim-ldap-csn-xx.txt | 239 The Abstract Syntax Notation One (ASN.1)[X680] type corresponding to
260 String Encoding Rules (GSER)[RFC3641] encoding of the ASN.1 type.
347 ChangeSequenceNumber syntax) whose corresponding ASN.1 type is
369 whose corresponding ASN.1 type is UTF8String. The rule evaluates to
384 ChangeSequenceNumber syntax) whose corresponding ASN.1 type is
426 syntax (e.g. the UTF8String syntax) whose corresponding ASN.1 type is
536 [RFC3641] Legg, S., "Generic String Encoding Rules (GSER) for ASN.1
548 Notation One (ASN.1): Specification of basic notation",
|