Re:The specs behind the specs – a deep-dive on ASN.1
by kevin_thibedeau on Thursday January 13, 2022 @05:54PM
(#29928173)
10 different string encodings is one problem.
[ Parent
| on HN ]
Re:The specs behind the specs – a deep-dive on ASN.1
by noselasd on Friday January 14, 2022 @04:43AM
(#29932465)
Is it ? You pick the one that fits your use, normally UTF8String these days
Re:The specs behind the specs – a deep-dive on ASN.1
by AceJohnny2 on Thursday January 13, 2022 @07:31PM
(#29929022)
Can one use UTF8?
The 90s were rough on text encoding, but it seems pretty settled now.
Re:The specs behind the specs – a deep-dive on ASN.1
by memling on Thursday January 13, 2022 @08:01PM
(#29929251)
> Can one use UTF8?
For new standards, yes. But ASN.1 was first specified in the '80s, and backwards compatibility is a thing. So really it depends on what you're doing: if you can start with a subset of ASN.1, which I think is done in MDER[0] and OER[1], you have a bit more freedom. But if you're working in legacy formats and standards that operate internationally, you could run into problems.
[0]: https://www.iso.org/standard/66717.html
[1]: see among others https://www.ntcip.org/document-numbers-and-status/
Re:The specs behind the specs – a deep-dive on ASN.1
by cryptonector on Friday January 14, 2022 @01:55PM
(#29938552)
Kerberos implementations generally just-send-whatever in IA5String fields. That means Windows sends UTF-8, and MIT Kerberos and Heimdal send whatever the user's locale uses. Windows doesn't normalize or anything. It works in that a) it interops when using ASCII names, b) it interops when using non-ASCII names in UTF-8 locales on Unix. It violates the spec, but it works.
Re:The specs behind the specs – a deep-dive on ASN.1
by cryptonector on Friday January 14, 2022 @01:58AM
(#29931387)
Stick to UTF8String. ASN.1 predates Unicode.
Re:The specs behind the specs – a deep-dive on ASN.1
by yrro on Friday January 14, 2022 @05:02AM
(#29932591)
Or IA5SString if you know, ahead of time, that you only need ASCII.
Re:The specs behind the specs – a deep-dive on ASN.1
by cryptonector on Friday January 14, 2022 @12:34PM
(#29937371)
Or do what many implementors do: just send whatever you have as whatever string type the protocol spec requires.