Xiaotian Zhou

Problem with Decoding of UTF8String in UPER

2

Hi, I found this potential inconsistency between encoding and decoding. When I define a utf8string type with a length constraints in UPER, the decoder could not decode the value encoded...

Constructed object extended component's length determinant check problem in UPER

4

Hi, I have encountered a problem with the length determinant check in Open Type when they include types with extensions in UPER. Suppose we have the following ASN.1 definition, ```...

Hi, I have found this potential issue when there are no defined extension items in the ASN.1 definition. Follow this example, ```asn1 SL-QoS-Profile-r16 ::= SEQUENCE { sl-PQI-r16 SL-PQI-r16 OPTIONAL, --...

Hi, I found the following potential issue in the ASN.1 code. When we encode sequence extensions, if all the extensions are absent, we should not encode the extension bit at...

Problem in ASN.1 UPER Enumerated Unpacking

1

Hi, I found that the enum_unpack in `lib/asn1/asn1_utils.cpp` has some issues. ```c SRSASN_CODE pack_enum(bit_ref& bref, uint32_t enum_val, uint32_t nbits, uint32_t nof_noext) { bool ext = enum_val >= nof_noext; HANDLE_CODE(bref.pack((bool)ext, 1));...

Support for Canonical UPER or more strict UPER decoder

1

The `pycrate` UPER decoder currently accepts several forms of non-canonical encodings. While this provides flexibility, it prevents users from using the library to validate strict protocol compliance. This feature request...

Non-Canonical encoding for Sequence Extension Group in ASN.1 UPER

1

Hi, In X.691 Section 19.9, it says ``` If all components values of the "ExtensionAdditionGroup" are missing then, the "ExtensionAdditionGroup" shall be encoded as a missing extension addition (i.e., the...

Hi, I found this issue when I was trying to compile the NR RRC specification. Here is a simplified example ``` Foo DEFINITIONS AUTOMATIC TAGS ::= BEGIN S1 ::= SEQUENCE...

Hi, I found that UPER and APER's decoder does not enforce the size constraint. In contrast, the encoder will enforce those constraints. For example (in the UPER's case), given this...