Ilya Etingof

Yes, PER support is on the TODO list!

Thank you for reporting this! Could I have a simple reproducer to understand the issue?

Which pyasn1 version you are using? My guess is that the actual problem is [here](https://github.com/MicrochipTech/aws-iot-zero-touch-secure-provisioning-kit/blob/802e506bdec57bb21d6c055f7c7818104cbae018/cert2certdef.py#L267). When you check for field value presence, starting from pyasn1 0.2.3, you should use the...

Interesting! Thank you for troubleshooting this issue! Error message is misleading. I will push a patch and report back.

I guess this is what happens when you run a decoder over some serialization. Is it that this serialization is being produced differently by 0.4.2 encoder? Or is it the...

This must have something to do with the `OpenType` support feature in pyasn1 `0.4.x` release. I guess that the third line: octet_string = decoder.decode(extension.getComponentByName('extnValue'), asn1Spec=OctetString())[0] tries to decode the OCTET...

Thank you for the debugging aid! I've been able to reproduce this. The root cause seems to be the fix to pyasn1_modules.rfc2459.Extension definition. In [ASN.1](http://web.mit.edu/freebsd/head/crypto/heimdal/lib/asn1/rfc2459.asn1) it looks like this: Extension...

Thank you for you PR! I'm not sure about unconditionally ignoring uninitilaized values approach. But your point (to preserve backward compatibility as much as possible while code evolves) is really...

Thank you for reporting this issue! It appears, that `openType` feature is not implemented for the native decoder. Let me see if we could add it there.

I think it should be fairly easy to do for both XML and JSON. I may be able to look into that unless you come up with a PR. ;-)...