Age | Commit message (Collapse) | Author | |
---|---|---|---|
2013-10-01 | Fix broken handling of default values for BIT STRINGs | Björn Gustavsson | |
For DER/PER/UPER, a value equal to the DEFAULT is not supposed to be encoded. BIT STRINGs values can be represented as Erlang terms in four different ways: as an integer, as a list of zeroes and ones, as a {Unused,Binary} tuple, or as an Erlang bitstring. When encoding a BIT STRING, only certain representations of BIT STRINGs values were recognized. All representations must be recognized. When decoding a DEFAULT value for a BIT STRING, the actual value given in the decoding would be either an integer or a list of zeroes and one (depending on how the literal was written in the specification). We expect that the default value should be in the same representation as any other BIT STRING value (i.e. by default an Erlang bitstring, or a list if the 'legacy_bitstring' option has been given, or as compact bitstring if 'compact_bitstring' has been given). | |||
2013-05-31 | Extend tests cases for BIT STRING | Björn Gustavsson | |
2013-05-31 | Normalize SIZE constraints to simplify backends | Björn Gustavsson | |
2013-05-31 | PER: Fix aligments bugs for short strings | Björn Gustavsson | |
The encoder wrongly assumed that a known multiplier string (such as IA5String) encoded as exactly 16 bits did not need to be aligned to an octet boundary. X.691 (07/2002) 27.5.7 says that it does. Since an OCTET STRING encoded to 16 bits (two octets) should not be aligned to an octet boundary, that means that asnct_imm:dec_string() needs an additional parameter to determine whether a string of a given length needs to be aligned. Furthermore, there is another subtle rule difference: An OCTET STRING which does not have fixed length is always aligned (in PER), but a known multiplier string is aligned if its upper bound is greater than or equal to 16. In encoding, make sure that short known multiplier strings and OCTET STRINGs with extensible sizes are not aligned when they are below the appropriate limit. | |||
2013-01-23 | testPrimStrings: Test some constraints | Björn Gustavsson | |
2012-12-19 | per: Fix encoding of OCTET STRINGs with fixed length of 256 or more | Björn Gustavsson | |
2012-12-06 | Optimize decoding of OCTET STRINGs | Björn Gustavsson | |
Decoding of fragmented OCTET STRINGs was only implemented when the size was constrained to a single value. While at it, support decoding fragmented OCTET STRINGS in all circumstances. | |||
2010-02-19 | OTP-8463 Support for EXTENSIBILITY IMPLIED and SET/SEQ OF NamedType is | Kenneth Lundin | |
added. |