Am 05.07.2020 um 08:59 schrieb Okan Konur:
I was asking this actually, we shouldn’t be needing more space. But we get
“not enough space” exception when we give the signed pdf path as inFile
parameter.
It could be that you need more space than in the old signature if you
have a very large signature, e.g. due to a large certificate chain. But
I don't know any reason why the signature space should be larger at each
iteration if the same signing mechanism is used.
Tilman
On 5 Jul 2020 Sun at 06:59 Tilman Hausherr <[email protected]> wrote:
Hi,
I have no idea why one would need "more space" for the signature area
when signing a signed document.
Tilman
Am 04.07.2020 um 21:38 schrieb Okan Konur:
Hi,
When we sign with our custom pki api, certificates and a smartcard
instead
of keytool generated pfx, we needed to increase signature size as
follows,
otherwise there was "not enough space" error.
signatureOptions.setPreferredSignatureSize(SignatureOptions.DEFAULT_SIGNATURE_SIZE
* 12)
This works fine. However, the problem is when signing an already signed
pdf.
Consecutive signing operations need more space naturally, but my
understanding was the signature size should be the same because this is
an
incremental update.
(We are not trying to concatenate to the previous signature dictionary.)
So do we need to increase the signature size multiplier for every other
signature operation on the same document?
Kind regards,
Okan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
