* 16 dercursor values for a PKIX Certificate
* 03 dercursor values for a PKIX Certificate Extension
- * 07 dercursor values for a Kerberos5 Ticket's unencrypted part
+ * 07 dercursor values for a Kerberos5 Ticket
* 14 dercursor values for a Kerberos5 Ticket's EncTicketPart
+Oh, and the walking paths that instruct the parser are very small too:
+
+ * 46 bytes for a PKIX Certificate
+ * 07 bytes for a PKIX Certificate Extension
+ * 33 bytes for a Kerberos5 Ticket
+ * 55 bytes for a Kerberos5 Ticket's EncTicketPart
+
Quite humble, isn't it?
* 4 nesting levels for a PKIX Certificate
* 1 nesting levels for a PKIX Certificate Extension
- * 4 nesting levels for a Kerberos5 Ticket's unencrypted part
+ * 5 nesting levels for a Kerberos5 Ticket's unencrypted part
* 5 nesting levels for a Kerberos5 Ticket's EncTicketPart
The reason that Kerberos is using a few more nesting levels is that it uses
*/
derwalk pack_Ticket [] = {
+ DER_PACK_ENTER | DER_TAG_APPLICATION (1), // Ticket [APPLICATION 1]
DER_PACK_ENTER | DER_TAG_SEQUENCE, // Ticket
DER_PACK_ENTER | DER_TAG_CONTEXT (0), // [0] tkt-vno
DER_PACK_STORE | DER_TAG_INTEGER, // tkt-vno (5)
DER_PACK_LEAVE, // enc-part
DER_PACK_LEAVE, // [3] enc-part
DER_PACK_LEAVE, // Ticket
+ DER_PACK_LEAVE, // Ticket [APPLICATION 1]
DER_PACK_END
};