Searched refs:ASN (Results 1 – 25 of 118) sorted by relevance
12345
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 …]
33 #define RC_FILE_DESC_0409 "ASN.1 Compiler"
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 …]
129 Syntax Notation One (ASN.1) [13] type definitions. ASN.1 type136 syntaxes and the X.500 ASN.1 types. To a large extent, the data138 described by ASN.1 types. This formal description can be exploited152 using ASN.1 type notation. All of the type notations defined in176 of attribute values of any syntax described by an ASN.1 type184 the LDAP and X.500 binary encoding (and possibly other ASN.1187 simply writing down an ASN.1 type definition for the syntax. These188 implicit definitions are also automatically extended if the ASN.1190 ASN.1 type definition, the various encodings and the component193 from ASN.1 type definitions.[all …]
12 ASN.1 Module Definition for the32 (ASN.1) definitions of the component matching rules into an33 appropriately identified ASN.1 module so that other specifications35 their own ASN.1 modules.49 Notation One (ASN.1) [ASN1] definitions of RFC 3687 into an50 appropriately identified ASN.1 module so that other specifications51 may reference these definitions from within their own ASN.1 modules.69 -- this ASN.1 module is part of RFC 3727; see the RFC itself128 The InformationFramework ASN.1 module from which the MATCHING-RULE138 This document collects together the ASN.1 definitions of the[all …]
39 If arbitrary ASN.1 types occur in the schema, then the mapping is85 4.2 Mapping ASN.1 Types to SLP Types .......................... 1792 4.3 Example ASN.1 Schema ...................................... 19145 RFC 2252 [8]. This syntax is a subset of the ASN.1/BER described in148 consistent mapping of ASN.1 based schemas to be translated in the SLP413 SLP Type ASN.1 Type LDAP Type478 ASN.1 has no concept of keyword attributes. Keyword attributes are479 translated into a "May" clause in the ASN.1 class definition for the515 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 …]
251 [ASN.1] represented in the dotted-decimal format (short descriptive324 This syntax corresponds to the AttributeTypeDescription ASN.1 type352 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.1474 The DirectoryString ASN.1 type allows a choice between the475 TeletexString, PrintableString, or UniversalString ASN.1 types from476 [ASN.1]. However, note that the chosen alternative is not indicated[all …]
86 4. Extending the LDAP ASN.1 Definition .............................990 4.4. General ASN.1 Extensibility ...............................10144 Syntax Notation - One (ASN.1) [X.680] definition to be made. This147 extension of the protocol's ASN.1 definition.245 Numerous elements of LDAP are described using ASN.1 [X.680] and are251 responseValue fields) described by ASN.1 and encoded using BER be472 4. Extending the LDAP ASN.1 Definition474 LDAP allows limited extension [Protocol, Section 4] of the LDAP ASN.1529 4.4. General ASN.1 Extensibility534 extensibility is implied where it is allowed per ASN.1 (i.e.,[all …]
74 Protocol elements are described using ASN.1 [X.680]. The term "BER-100 This syntax corresponds to the SubtreeSpecification ASN.1 type101 described in [X.501], Section 11.3. This ASN.1 data type definition463 application of [RFC3641]. Since the SubtreeSpecification ASN.1 type466 for any extension to the SubtreeSpecification ASN.1 type can be532 [X.680] ITU-T, "Abstract Syntax Notation One (ASN.1) -535 [X.690] ITU-T, "Specification of ASN.1 encoding rules: Basic,571 [RFC3641] Legg, S., "Generic String Encoding Rules (GSER) for ASN.1
45 The structure of a DN [X.501] is described in terms of ASN.1 [X.680].70 RECOMMENDED algorithm for converting a DN from its ASN.1 structured72 from a string to an ASN.1 structured representation.75 from its ASN.1 structured representation to a string, all algorithms119 2. Converting DistinguishedName from ASN.1 to a String121 X.501 [X.501] defines the ASN.1 [X.680] structure of distinguished136 distinguished name from an ASN.1-structured representation to a UTF-8158 When converting from an ASN.1 RelativeDistinguishedName to a string,194 2.4. Converting an AttributeValue from ASN.1 to a String518 Syntax Notation One (ASN.1) - Specification of Basic[all …]
160 operations and use the LDAP Abstract Syntax Notation One (ASN.1)348 of the following ASN.1:376 following ASN.1:421 the following ASN.1:514 message, it contains the BER-encoding of the following ASN.1:543 The requestValue contains the BER-encoding of the following ASN.1:749 (ASN.1): Specification of basic notation"752 "Information technology - ASN.1 encoding rules:
297 encapsulated. Each message type consists of an ASN.1 identifier in302 implicit in the protocol's ASN.1 defined in [RFC4511].312 [RFC4511]. Each authentication choice consists of an ASN.1355 an ASN.1 identifier in the form of a keyword and a non-negative372 value consists of an ASN.1 identifier in the form of a keyword and a389 a type of assertion. Each Filter CHOICE consists of an ASN.1410 consists of an ASN.1 identifier in the form of a keyword and a non-637 (ASN.1) - Specification of Basic Notation", X.680(2002)
87 Protocol elements are described using ASN.1 [X.680] with implicit255 Syntax Notation One (ASN.1) - Specification of Basic260 "Specification of ASN.1 encoding rules: Basic Encoding
63 Protocol elements are described using ASN.1 [X.680] with implicit307 (ASN.1) - Specification of Basic Notation", X.680(1997)311 Standardization Sector, "Specification of ASN.1 encoding
101 Appendix B. Complete ASN.1 Definition .............................54251 ([ASN.1]) and is transferred using a subset of ASN.1 Basic Encoding256 is implied where it is allowed per ASN.1 (i.e., sequence, set,258 (...) have been supplied in ASN.1 types that are explicitly324 The ASN.1 type Controls is defined in Section 4.1.11.377 strings of LDAPString type encode as ASN.1 OCTET STRING types, the797 of ASN.1, and BER-encoded according to Section 5.1, it also follows2107 zero bytes. Values that are defined in terms of ASN.1 and BER-2341 Basic Encoding Rules [BER] of [ASN.1] with the following2366 These restrictions do not apply to ASN.1 types encapsulated inside of[all …]
93 Protocol elements are described using ASN.1 [X.680] with implicit318 Syntax Notation One (ASN.1) - Specification of Basic323 "Specification of ASN.1 encoding rules: Basic Encoding
1 A Layman's Guide to a Subset of ASN.1, BER, and DER22 subset of OSI's Abstract Syntax Notation One (ASN.1), Basic57 OSI's method of specifying abstract objects is called ASN.161 defined in X.209). ASN.1 is a flexible notation that allows66 each ASN.1 type as a string of eight-bit octets. There is70 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 of77 ASN.1 types and their BER and DER encodings. Sections 2-478 give an overview of ASN.1, BER, and DER, in that order.[all …]
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 syntax70 2) using eSNACC, compile your ASN.1 specifications and95 BER. Currently primitive ASN.1 types, DN, and RDN
35 -- following ORAddress may not conform original def. in ASN.1
239 The Abstract Syntax Notation One (ASN.1)[X680] type corresponding to260 String Encoding Rules (GSER)[RFC3641] encoding of the ASN.1 type.347 ChangeSequenceNumber syntax) whose corresponding ASN.1 type is369 whose corresponding ASN.1 type is UTF8String. The rule evaluates to384 ChangeSequenceNumber syntax) whose corresponding ASN.1 type is426 syntax (e.g. the UTF8String syntax) whose corresponding ASN.1 type is536 [RFC3641] Legg, S., "Generic String Encoding Rules (GSER) for ASN.1548 Notation One (ASN.1): Specification of basic notation",
148 specific Abstract Syntax Notation One (ASN.1) [X680] encoding rules,216 does not have an associated ASN.1 type [SYNTAX], or if the nominated236 according to the Basic Encoding Rules [X690] of ASN.1. This option244 according to the Distinguished Encoding Rules [X690] of ASN.1.254 be the identifier of the NamedType [X680] in the LDAP ASN.1480 [RFC3641] Legg, S., "Generic String Encoding Rules (GSER) for ASN.1489 ASN.1 Types", draft-legg-xed-rxer-00.txt, a work in494 (ASN.1): Specification of basic notation.505 Information Technology - ASN.1 encoding rules:
52 long ASN; /* Address space number */ member
7 Description: OpenLDAP Lightweight ASN.1 Basic Encoding Rules library
240 * Fixed various read buffer overruns processing ASN.1 strings ([CVE-2021-3712])396 * Constructed ASN.1 types with a recursive definition could exceed the521 * Constructed ASN.1 types with a recursive definition could exceed the567 * Prevent ASN.1 BIO excessive memory allocation ([CVE-2016-2109])626 * ASN.1 structure reuse memory corruption fix ([CVE-2015-0287])668 * Prevent ASN.1 BIO excessive memory allocation ([CVE-2016-2109])722 * ASN.1 structure reuse memory corruption fix ([CVE-2015-0287])846 * ASN.1 structure reuse memory corruption fix ([CVE-2015-0287])1087 * New ASN.1 mini-compiler that's usable through the OpenSSL1089 * Added support for ASN.1 indefinite length constructed encoding.[all …]
8 # They are specified via ASN.1 schemas and some prose. Basic encoding