You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pdfbox.apache.org by Gavin Reid <ga...@pseudocoder.co.uk> on 2019/01/03 07:44:46 UTC
Re: Certifcate Based AES256
I’ve just managed to test my code vs 2.0.14……..-126.jar and it appears to be working very well. The reader has confirmed 256 AES bit encryption.
Thank you ever so much for the swift response and fix.
I presume I now just wait for 2.0.14 to have a full release?
Kind Regards
Gavin
> On 22 Dec 2018, at 16:20, Tilman Hausherr <TH...@t-online.de> wrote:
>
> Am 22.12.2018 um 12:02 schrieb Gavin Reid:
>> AES256 is a symmetric cypher, my certificate is only used to encrypt the AES256 key, the AES256 key is generated fresh each time a document is encrypted.
>> Each certificate is for each recipient.
>
> Never mind. In the meantime, I created an AES256 encrypted file with another software so I could see how the result file looks like (the PDF specification is not really clear to me), and I also managed to decrypt it. So the "only" thing missing now is encryption.
>
> Tilman
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: Certifcate Based AES256
Posted by Tilman Hausherr <TH...@t-online.de>.
This is mostly because of decryption. In theory, some user could come up
with an AES128 encrypted file and fail to decrypt it with PDFBox.
It is also because of curiosity. I was able to get AES256 working but
not AES128 and I wonder why. However I have not worked on it since
creating the issue. Maybe I'll find am idea after doing nothing on it
for some time.
Tilman
Am 07.01.2019 um 10:38 schrieb gavinreid@pseudocoder.co.uk:
> I noticed that there is a new JIRA related to AES 128 bit.
>
> Is there any value to be gained by being able to specify the
> encryption algorithm to be used?
>
> With the current snapshot the behaviour is as follows:
>
> Key Length 40 = RC4
> Key Length 128 = RC4
> Key Length 256 = AES
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: Certifcate Based AES256
Posted by ga...@pseudocoder.co.uk.
I noticed that there is a new JIRA related to AES 128 bit.
Is there any value to be gained by being able to specify the
encryption algorithm to be used?
With the current snapshot the behaviour is as follows:
Key Length 40 = RC4
Key Length 128 = RC4
Key Length 256 = AES
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: Certifcate Based AES256
Posted by Tilman Hausherr <TH...@t-online.de>.
Am 03.01.2019 um 08:44 schrieb Gavin Reid:
> I’ve just managed to test my code vs 2.0.14……..-126.jar and it appears to be working very well. The reader has confirmed 256 AES bit encryption.
> Thank you ever so much for the swift response and fix.
> I presume I now just wait for 2.0.14 to have a full release?
Yes. Probably in 2-3 months.
Tilman
>
>
> Kind Regards
>
> Gavin
>
>> On 22 Dec 2018, at 16:20, Tilman Hausherr <TH...@t-online.de> wrote:
>>
>> Am 22.12.2018 um 12:02 schrieb Gavin Reid:
>>> AES256 is a symmetric cypher, my certificate is only used to encrypt the AES256 key, the AES256 key is generated fresh each time a document is encrypted.
>>> Each certificate is for each recipient.
>> Never mind. In the meantime, I created an AES256 encrypted file with another software so I could see how the result file looks like (the PDF specification is not really clear to me), and I also managed to decrypt it. So the "only" thing missing now is encryption.
>>
>> Tilman
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: users-help@pdfbox.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org