#asn1js — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #asn1js, aggregated by home.social.
-
In new #ASN1js version2.1.0I changed the logic of the shown #ASN1 field names due to research started with GitHub issue #102:
Previously it would have shown simply asissuer, but fixing another issue I had a (kinda) regression and it shown only the CHOICE identifier (in this caserdnSequence).
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 thenotBefore 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. -
In new #ASN1js version2.1.0I changed the logic of the shown #ASN1 field names due to research started with GitHub issue #102:
Previously it would have shown simply asissuer, but fixing another issue I had a (kinda) regression and it shown only the CHOICE identifier (in this caserdnSequence).
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 thenotBefore 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. -
In new #ASN1js version2.1.0I changed the logic of the shown #ASN1 field names due to research started with GitHub issue #102:
Previously it would have shown simply asissuer, but fixing another issue I had a (kinda) regression and it shown only the CHOICE identifier (in this caserdnSequence).
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 thenotBefore 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. -
In new #ASN1js version2.1.0I changed the logic of the shown #ASN1 field names due to research started with GitHub issue #102:
Previously it would have shown simply asissuer, but fixing another issue I had a (kinda) regression and it shown only the CHOICE identifier (in this caserdnSequence).
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 thenotBefore 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. -
-
-
-
-
-
Added PKCS#10 support to ASN1js
https://f.lapo.it/display/6a1cc041-1364-ee66-a032-02f373674423