[Poppler-bugs] [Bug 99416] Sign PDF with digital signature

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99416

--- Comment #45 from Hans-Ulrich Jüttner <huj at froreich-bioscientia.de> ---
(In reply to Adrian Johnson from comment #44)
> (In reply to Albert Astals Cid from comment #43)
> > This is what needs to happen, be it reread or ideally a less extensive
> > operation, but after sign is called, things need to keep returning valid
> > information.
> 
> It is probably sufficient to just update the signature and byte offsets in
> the in memory object.

(In reply to Albert Astals Cid from comment #43)
> (In reply to Adrian Johnson from comment #42)
> > I'm not familiar with the qt5 interface. There a a couple of options:
> > - reread the document after signing so the in memory copy is consistent with
> > the on disk copy
> 
> This is what needs to happen, be it reread or ideally a less extensive
> operation, but after sign is called, things need to keep returning valid
> information.
> 
> Hans what do you say would be invalid and why?

The in memory ByteRange object contains numbers 9999999999 and generates a
string "/ByteRange [0 9999999999 9999999999 9999999999 ]" if written to disk.
The in memory Contents object contains a string with a signature not calculated
over the byte ranges which should be signed.

> 
> > - document the signing as a "save a copy" operation. ie the saved copy will
> > be different to the in memory copy. And fix the code so the in memory copy
> > is not changed.
> 
> This doesn't make sense, remember you're not "signing the document", but
> signining an anotation of the document, so this is not even a function on
> the document level, but at the annotation level.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/poppler-bugs/attachments/20170915/124c3632/attachment.html>