New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Qualified Certificate Statements (qcStatements) (1.3.6.1.5.5.7.1.3) #231
Comments
@april April, this is a "rare used" extension with a more or less primitive encoding in there: SEQUENCE {
SEQUENCE {
OBJECT IDENTIFIER etsiQcsCompliance (0 4 0 1862 1 1)
}
SEQUENCE {
OBJECT IDENTIFIER '0 4 0 1862 1 6'
SEQUENCE {
OBJECT IDENTIFIER '0 4 0 1862 1 6 3'
}
}
SEQUENCE {
OBJECT IDENTIFIER '0 4 0 1862 1 5'
SEQUENCE {
SEQUENCE {
IA5String 'https://www.quovadisglobal.com/repository'
PrintableString 'en'
}
}
}
} Do you really need support from PKI.js for such data? From my PoV I think you could use only ASN1js decoding features: it would not provide your a schema verification, but you will have all necessary data in there. const asn1 = asn1js.fromBER(buffer); |
Let’s add it, it’s becoming more common. |
The EU seems to be on a push to use it, and they just released a Firefox extension that depends upon it. I honestly didn’t know it existed until then. :) |
Signed-off-by: YuryStrozhevsky <yury@strozhevsky.com>
@april I made changes, but want to warn you that it is almost useless - in the extension mandatory part is |
You can see a cert with this here:
https://www.zijnjullieeraluit.nl/
Here is the object:
For more information, see:
https://tools.ietf.org/html/rfc3739.html
https://www.etsi.org/deliver/etsi_ts/101800_101899/101862/01.03.03_60/ts_101862v010303p.pdf
Thanks as always!
The text was updated successfully, but these errors were encountered: