home.social

#asn1js — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #asn1js, aggregated by home.social.

  1. In new #ASN1js version 2.1.0 I changed the logic of the shown #ASN1 field names due to research started with GitHub issue #102:
    Previously it would have shown simply as issuer, but fixing another issue I had a (kinda) regression and it shown only the CHOICE identifier (in this case rdnSequence).
    In the end, I think that probably the best choice is to show both names, the base one as it usually is more useful to identify the field, but the CHOICE name to know which sub-case this is. This leads to a bit of uninteresting info such as the notBefore utcTime UTCTime, but that's the (small) price to be paid.
    This was a delicate change, so first thing I extended the test harness in order to check that a few important examples decode to what is expected.
  2. In new #ASN1js version 2.1.0 I changed the logic of the shown #ASN1 field names due to research started with GitHub issue #102:
    Previously it would have shown simply as issuer, but fixing another issue I had a (kinda) regression and it shown only the CHOICE identifier (in this case rdnSequence).
    In the end, I think that probably the best choice is to show both names, the base one as it usually is more useful to identify the field, but the CHOICE name to know which sub-case this is. This leads to a bit of uninteresting info such as the notBefore utcTime UTCTime, but that's the (small) price to be paid.
    This was a delicate change, so first thing I extended the test harness in order to check that a few important examples decode to what is expected.
  3. In new #ASN1js version 2.1.0 I changed the logic of the shown #ASN1 field names due to research started with GitHub issue #102:
    Previously it would have shown simply as issuer, but fixing another issue I had a (kinda) regression and it shown only the CHOICE identifier (in this case rdnSequence).
    In the end, I think that probably the best choice is to show both names, the base one as it usually is more useful to identify the field, but the CHOICE name to know which sub-case this is. This leads to a bit of uninteresting info such as the notBefore utcTime UTCTime, but that's the (small) price to be paid.
    This was a delicate change, so first thing I extended the test harness in order to check that a few important examples decode to what is expected.
  4. In new #ASN1js version 2.1.0 I changed the logic of the shown #ASN1 field names due to research started with GitHub issue #102:
    Previously it would have shown simply as issuer, but fixing another issue I had a (kinda) regression and it shown only the CHOICE identifier (in this case rdnSequence).
    In the end, I think that probably the best choice is to show both names, the base one as it usually is more useful to identify the field, but the CHOICE name to know which sub-case this is. This leads to a bit of uninteresting info such as the notBefore utcTime UTCTime, but that's the (small) price to be paid.
    This was a delicate change, so first thing I extended the test harness in order to check that a few important examples decode to what is expected.
  5. New #ASN1js feature: showing field names, as taken from #ASN1 module definitions parsed right out of #RFC.
    Consider it beta for now (currently supports only X.509 and CMS definitions, but this will change in the future).