Valery Buchinsky

https://github.com/vbuch/node-signpdf/issues/79#issuecomment-1803905603

Thank you for the input @symbianm It was just the thing I was about to do on the placeholder-pdf-lib PR. Here is [my take on it](https://github.com/vbuch/node-signpdf/pull/203/files#diff-9d93987e29f38a35006348def3418c77b14fe38616c75302236f4519350c56f1R92) and here is [how...

@DesFid I'm having a hard time figuring out where in the specs these are flagged. Could you help me out? I was looking at [the spec for 1.3](https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/pdfreference1.3.pdf). Maybe this...

Just a note to anyone interested in implementing LTV: This is where that starts: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277804/01.01.01_60/ts_10277804v010101p.pdf

Could this be related? https://github.com/digitalbazaar/forge/issues/975 Does the proposed patch to node-forge fix it? Not really sure. The issue has stayed for quite some months (sorry for that, maintainer's fault). Did...

@prdufresne I just see your comment now. I'm sorry you had hard time with that. At the time you wrote it this was already demoed long ago in the tests....

@Philip-Kazmeier you are right. The initial idea of node-signpdf was to only provide the cryptgraphic part of the signing which is something Adobe will do in your use-case. Now this...

@20manas 2.0.0 already has some (limited) TS types generated through JSDoc. Much more will be availale in 3+

@hscstudio I will include your example in 3+

https://github.com/vbuch/node-signpdf/releases/tag/v3.0.0