Will Bond

The OID 1.2.643.2.2.19 appears to identify gostR3410-2001. https://tools.ietf.org/html/rfc4357.html Someone would have to make a PR that added that OID and related ASN.1 definitions around https://github.com/wbond/asn1crypto/blob/master/asn1crypto/keys.py#L924-L989.

> I haven't followed these changes, but do we really need this level of data manipulation (i.e. breaking every URI into all its components and reassembling them) to populate the...

If you've got a fix and the time to submit it, I'm sure @joernheissler or myself can review it. More robust tests for ldap is certainly welcome if you've got...

@defacto64 Is the tagged field an implicit or explicit field? If you look through the various modules in the package (other than `core.py` you should be able to find some...

I'd be open to a PR if you'd like to see such a feature.

So in asn1crypto, the item access syntax performs direct ASN.1 structure access. As @joernheissler explained, the way that RSA is encoded is a double encoding, thus it takes two steps...

Would you happen to have any example files that utilize the ASN.1 from RFC 5126? This seems to be the ASN.1 provided by that RFC: ``` DEFINITIONS EXPLICIT TAGS ::=...

Currently length restrictions are not enforced in the structure definitions. I wouldn't be opposed to a proposal for implementing them. I mostly just didn't really run into situations myself where...

I think the key aspect of this will ideally be a couple of test fixtures that at least cover a good chunk of the definitions. I realize exhaustive coverage may...

I just glanced at it now. One thing is that asn1crypto uses `under_score_notation` for field names, whereas so far you are using `lowerCamelCase`.