Closed donskov closed 4 years ago
@donskov Hope today we discussed all via Skype. So I assume you will close the PR.
Out of curiosity why not handle the extension explicitly as in this PR?
@YuryStrozhevsky sad that:
asn1js
and parse itI think we can keep this extension on pkijs
, but I am not this package maintainer
Personally I would include it in PKIjs, we have many other extensions, some that are not standards, but I dont feel super strongly as long as pv-certificate-viewer supports it.
@rmhrisk Agree with you @YuryStrozhevsky What do you think?
I would like to prevent pkijs from including a garbage. The extension is only needed to show a values on certificate viewer, nothing else. There would be no application that would change or make the application. The other garbage-like extensions were included by a request from Mozilla. Now it is only an internal request and we do can prevent pkijs from including unnecessary code.
The reason this extension is used is to enable applications that do signing to pick a timestamp service that should be used for that signature. The display of the extension is really just a diagnostic.
I can accept it not being in PKIjs but when we do that we just need to be sure we apply the rules holistically on what is in vs out.
Many of the MSFT extensions, such as templates are "garbage" to a degree as well, they are used more than this one given Microsoft's ubiquity though.
In any event im fine with this outcome but want to make sure we apply rules uniformly.
Related with https://github.com/PeculiarVentures/pv-certificates-viewer/issues/46 Class from https://www.adobe.com/devnet-docs/etk_deprecated/tools/DigSig/oids.html
Schema
Certificate with extension: