| | <<<Back 1 day (to 2020/03/06) | Fwd 1 day (to 2020/03/08)>>> | 20200307 |
| jarindyk2 | thanks Robin, looking forward to it, is it an off-by-one bug? | 21:39.18 |
| | also is it possible to show something like "the signature is valid but there have been edits since signing" or "the document is unchanged since signing" like mutool sign does? (pdfsign.c) or is that obsolete and gonna get replaced by what show_sig_dialog does (pdf_validate_signature())? | 21:43.42 |
| | or does the signature get invalidated after edits? | 21:44.09 |
| | I dunno what's really the difference between pdfsign.c (mutool) and mupdf-gl's pdf_validate_signature, pdfsign.c seems to use pdf_new_indirect in a loop and runs process_field on ctx, doc, and field, and then based on opts, it runs verify_signature(ctx, doc, field) which basically does what gl-form.c does apart from using "pdf_signature_incremental_change_since_signing" for edits, and based on its return | 21:50.57 |
| | value it says "the sign is valid but there have been edits since signing" and "the document is unchanged since signing" otherwise digest error | 21:51.03 |
| | whereas gl-form.c calls pdf_validate_signature instead of pdf_signature_incr... which mentions locked fields | 21:52.56 |
| | and mutool's sign doesn't | 21:53.04 |
| | so there's some inconsistency, and not sure which should be preferred or if they are different and could be merged | 21:53.59 |
| | I'll mess around with it once you push the fix | 21:54.53 |
| | <<<Back 1 day (to 2020/03/06) | Forward 1 day (to 2020/03/08)>>> | |
Log of #mupdf at irc.freenode.net.