Kim Gräsman

The title no longer agrees with the backtrace in the description. I guess the asn.1 syntax was fixed? It looks like you're running into https://github.com/kimgr/asn1ate/issues/74. Try an older version of...

Hi @vanrein, I went back to the X.680 spec (available from here: https://www.itu.int/rec/T-REC-X.681) to find this, and it looks like you need better support for `BitStringValue` and `SequenceOfValue` for these...

I haven't seen the `GeneralString (IA5String)` constraint syntax before, and I'm not sure what it means. Do you know? If you're just interested in getting this to work on your...

I think you need to be more specific for me to be able to help. It's quite possible that the Kerberos spec contains more constructs that asn1ate doesn't support.

Here's a clue: > (line:132, col:30) If you know your way around ASN.1, you may be able to change it to something simpler. I wish asn1ate's parser error reporting was...

I don't think it's size-related, there's probably just some ASN.1 syntax in the file that isn't supported by asn1ate. I know most Kerberos specs use advanced ASN.1 features, so they're...

@SuperXiaoxiong > 135 msg-type [2] INTEGER (10 -- AS -- | 12 -- TGS --), I suspect this constrained integer isn't supported by asn1ate. you can just remove the constraint...

@SuperXiaoxiong I'm glad to hear! Was this the only change you had to make to parse the Kerberos ASN.1? If so, it sounds like a priority to improve asn1ate support...

Is that all you see, or do you also get a python traceback?

Most of asn1ate is based on X.680 and this is actually mentioned in clause 37. I hadn't seen that before, and we don't yet have any handling of such "well-known"...