3 ms·
I did digital signature work for an ARINC spec, which sounds a bit like OOXML, and I have a slightly different take, although to be clear I spent about six mont
by hinkley 3y ago
I did digital signature work for an ARINC spec, which sounds a bit like OOXML, and I have a slightly different take, although to be clear I spent about six months getting a prototype to function, and three more years making it performant and bullet proof.
A couple years ago I wanted to link the spec to my resume and found it was not freely available. Now I’d like to see a copy to verify whether in retrospect I missed anything.
Among the decisions I made:
- provide no metadata until the signature has verified.
- implement your own file extraction logic, use the same logic for locating elements and assets
- don’t touch the file system until the signature has verified
- implement metadata functions using the same code used for locating elements
- use prefetch for xml namespaces, disable network requests
- implement a wrapper around getElementByID, throw an error if multiple elements are ever found (including searching from the root element).
- only extract files and elements that were signed
- canonicalize paths
- implement multiple warnings for impending cert expiration
- be very, very careful if you allow multiple signatures
- watch out for one team demanding requirements that prevent their counterparts from operating
- get used to saying, “no”, but offering workarounds