On 6/18/24 18:42, Hans Hagen via ntg-context wrote: > On 6/18/2024 6:26 PM, Pablo Rodriguez via ntg-context wrote: >> [...] >> As far as I know, this has to be a reason for digest mismatch (or a huge >> hash collision). > > could be (depends on checker) but it we change that we also need to > change the verify offset (so two patches)
I have just discovered that verify didn’t work with the binary. Figuring out now how to testing with the library. >> Signatures in PDF-2.0 loose their possibility of other ranges than the >> entire file. Their use is simply not allowed. > > so more limited then to basically two ranges It makes sense and it is recommended for PDF-1.x. >>>> Sorry for insisting, but please don’t require plaintext password in the >>>> command line (again, OpenSSL prompts for it). >>> not if we use the library >> >> Weird, on both Linux64 and Win64, the openssl runner requires the >> openssl binary to be installed. > > i meant the --library option In that case, when --library is not invoked, we might avoid mandating the password in plain text. Many thanks for your help, Pablo ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___________________________________________________________________________________
