<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Sign PDF with digital signature"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99416#c49">Comment # 49</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Sign PDF with digital signature"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99416">bug 99416</a>
from <span class="vcard"><a class="email" href="mailto:ajohnson@redneon.com" title="Adrian Johnson <ajohnson@redneon.com>"> <span class="fn">Adrian Johnson</span></a>
</span></b>
<pre>(In reply to Hans-Ulrich Jüttner from <a href="show_bug.cgi?id=99416#c48">comment #48</a>)
<span class="quote">> I think that re-reading a document which just has been written with poppler
> and writing it again whithout changes should produce an identical document.</span >
Should does not mean it always will. It introduces a constraint on poppler that
prevents any future changes that alter that assumption.
I still have not seen a good explanation for why the you think the signing
should work this way.
<span class="quote">> But with the multiple spaces in the ByteRange on disk this would not be the
> case. Moreover, multiple spaces separating objects in PFD files are not
> allowed by more restrictive standards like PDF/A.</span >
Then we can use '0's. But in any case we don't support PDF/A.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>