<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#c46">Comment # 46</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:huj@froreich-bioscientia.de" title="Hans-Ulrich Jüttner <huj@froreich-bioscientia.de>"> <span class="fn">Hans-Ulrich Jüttner</span></a>
</span></b>
<pre>(In reply to Adrian Johnson from <a href="show_bug.cgi?id=99416#c44">comment #44</a>)
<span class="quote">> (In reply to Albert Astals Cid from <a href="show_bug.cgi?id=99416#c43">comment #43</a>)
> > 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.</span >
With the Contents object I see no problem replacing it with the correct
signature
value. However, the ByteRange object on disk is a string with multiple spaces,
e.g. "/ByteRange [0 103562 108976 311 ]". These multiple spaces
can't be represented in the ByteRange object in memory as it is an array of
integers. But if these multiple spaces are removed the signature will be
invalidated since the hash is calculated over a string including these spaces.
Before the patch (3) of Adrian this problem was avoided by not producing such
multiple spaces.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>