3 ms·
That assumes the correct number of ASN.1 parsers in the kernel is "1". I would strictly prefer my kernel to include "0" (zero, nil, none) ASN.1 parsers. It's a
by stefan_ 6y ago
That assumes the correct number of ASN.1 parsers in the kernel is "1". I would strictly prefer my kernel to include "0" (zero, nil, none) ASN.1 parsers. It's a trash spec designed by committee that probably needs its own bytecode machine to be parsed safely (that certainly is the track record of ASN.1 parsers in the wild).
- ZeroGravitas 6y agoI think there was a recent kefuffle in the python community because they wanted to depend on a Rust library to parse ASN.1 and some more obscure platforms weren't ready for that change.
- comfydragon 6y agoNot in core Python, but in a widely-used library, yes. https://github.com/pyca/cryptography/issues/5771 https://github.com/pyca/cryptography/issues/5771
- rwmj 6y agoHow would you suggest that the kernel interoperates with systems that need ASN.1 such as X.509 encryption, CIFS filesystems, or BER encoding in the H.323 ITU standard?
- tremon 6y agoFor example, by having a userspace helper for it. Pretty similar to the same way that the kernel itself doesn't do firmware patching, but relies on userspace to handle the opaque blobs.
- rwmj 6y agoFirmware patching happens rarely, but decoding packets in the firewall would be far slower and more fragile if it required calling out to a userspace process.