You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pdfbox.apache.org by ga...@pseudocoder.co.uk on 2018/12/21 09:09:03 UTC
Certifcate Based AES256
I'm using PDFBox 2.0.12 and I’m attempting to encrypt a PDF Document
using 256 bit keylength.
But I’m receiving an Error that this is not supported, but it appears
that from the documentation that 256 IS supported but only for
passwords.
Is there a mechanism for using the current working implementation of
passwords with the Certificate encryption?
(or any plans to allow 256 with certificates?)
Regards
Gavin
---------------------------------------------------------------------
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 21.12.2018 um 14:35 schrieb gavinreid@pseudocoder.co.uk:
> Are you sure its RC4?
> I'd seen the following in
> PublicKeySecurityHandler.prepareDocumentForEncryption()
>
> key = KeyGenerator.getInstance("AES");
>
> if its really using RC4 I'm going to take a little nap until I feel
> well again.
Reading further there makes me think that this is used to compute a seed.
Tilman
>
> Gavin
>
>
> Quoting Tilman Hausherr <TH...@t-online.de>:
>
>> Hi,
>>
>> Now I get it... I had a look at the code, we do not support AES at
>> all for public keys. Passing an 128 bit key results in a 128-Bit RC4
>> encryption LOL.
>>
>>
>> I've created an issue for this:
>> https://jira.apache.org/jira/browse/PDFBOX-4413
>> Please register and click to watch the issue.
>>
>> I suspect that much of it is already available in the base class, but
>> PublicKeySecurityHandler.prepareDocumentForEncryption() is
>> definitively old stuff.
>>
>> Tilman
>>
>>
>>
>> Am 21.12.2018 um 10:29 schrieb gavinreid@pseudocoder.co.uk:
>>> As requested
>>>
>>> Exception in thread "main" java.io.IOException: 256 bit key length
>>> is not supported yet for public key security
>>> at
>>> org.apache.pdfbox.pdmodel.encryption.PublicKeySecurityHandler.prepareDocumentForEncryption(PublicKeySecurityHandler.java:286)
>>> at org.apache.pdfbox.pdfwriter.COSWriter.write(COSWriter.java:1313)
>>> at org.apache.pdfbox.pdfwriter.COSWriter.write(COSWriter.java:1262)
>>> at org.apache.pdfbox.pdmodel.PDDocument.save(PDDocument.java:1335)
>>>
>>> public static void main(String args[]) throws Exception {
>>> PDDocument doc = PDDocument.load(new
>>> File("Resources/sample.pdf"));
>>>
>>> PublicKeyProtectionPolicy policy = new
>>> PublicKeyProtectionPolicy();
>>> PublicKeyRecipient recip = new PublicKeyRecipient();
>>> AccessPermission ap = new AccessPermission();
>>> ap.setCanModify(false);
>>> recip.setPermission(ap);
>>> InputStream inStream = new
>>> FileInputStream("Resources/CertExchange.cer");
>>> CertificateFactory cf =
>>> CertificateFactory.getInstance("X.509");
>>> InputStream is =
>>> Files.newInputStream(Paths.get("Resources/keystore.pem"));
>>> String keyStorePassword = "123456";
>>> KeyStore keyStore =
>>> KeyStore.getInstance(KeyStore.getDefaultType());
>>> keyStore.load(is, keyStorePassword.toCharArray());
>>> X509Certificate certificate = (X509Certificate)
>>> keyStore.getCertificate("Gavin");
>>>
>>> recip.setX509(certificate); // set the recipient's certificate
>>> policy.addRecipient(recip);
>>> policy.setEncryptionKeyLength(256); // the document will be
>>> encrypted with 128 bits secret key
>>> doc.protect(policy);
>>> doc.save(new FileOutputStream("Resources/output.pdf"));
>>>
>>> }
>>>
>>>
>>>
>>> Quoting Tilman Hausherr <TH...@t-online.de>:
>>>
>>>> Hi,
>>>> Please provide a stack trace and a working example, i.e. code and a
>>>> certificate. Please upload these somewhere, attachments are usually
>>>> deleted by the mailing list software.
>>>> Tilman
>>>>
>>>> Am 21.12.2018 um 10:09 schrieb gavinreid@pseudocoder.co.uk:
>>>>>
>>>>> I'm using PDFBox 2.0.12 and I’m attempting to encrypt a PDF
>>>>> Document using 256 bit keylength.
>>>>>
>>>>> But I’m receiving an Error that this is not supported, but it
>>>>> appears that from the documentation that 256 IS supported but only
>>>>> for passwords.
>>>>>
>>>>> Is there a mechanism for using the current working implementation
>>>>> of passwords with the Certificate encryption?
>>>>> (or any plans to allow 256 with certificates?)
>>>>>
>>>>> Regards
>>>>>
>>>>> Gavin
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>
>
>
>
>
> ---------------------------------------------------------------------
> 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
Re: Certifcate Based AES256
Posted by Gavin Reid <ga...@pseudocoder.co.uk>.
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>.
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
Re: Certifcate Based AES256
Posted by Gavin Reid <ga...@pseudocoder.co.uk>.
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.
Regards
Gavin
Sent from my iPhone
> On Dec 21, 2018, at 22:08, Tilman Hausherr <TH...@t-online.de> wrote:
>
>> Am 21.12.2018 um 14:35 schrieb gavinreid@pseudocoder.co.uk:
>> if its really using RC4 I'm going to take a little nap until I feel well again.
>
>
> Can you upload an AES256 public key encrypted document somewhere? I'm wondering if I missed something in the encryption dictionary.
>
> 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>.
Am 21.12.2018 um 14:35 schrieb gavinreid@pseudocoder.co.uk:
> if its really using RC4 I'm going to take a little nap until I feel
> well again.
Can you upload an AES256 public key encrypted document somewhere? I'm
wondering if I missed something in the encryption dictionary.
Tilman
---------------------------------------------------------------------
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.
Are you sure its RC4?
I'd seen the following in
PublicKeySecurityHandler.prepareDocumentForEncryption()
key = KeyGenerator.getInstance("AES");
if its really using RC4 I'm going to take a little nap until I feel
well again.
Gavin
Quoting Tilman Hausherr <TH...@t-online.de>:
> Hi,
>
> Now I get it... I had a look at the code, we do not support AES at
> all for public keys. Passing an 128 bit key results in a 128-Bit RC4
> encryption LOL.
>
>
> I've created an issue for this:
> https://jira.apache.org/jira/browse/PDFBOX-4413
> Please register and click to watch the issue.
>
> I suspect that much of it is already available in the base class,
> but PublicKeySecurityHandler.prepareDocumentForEncryption() is
> definitively old stuff.
>
> Tilman
>
>
>
> Am 21.12.2018 um 10:29 schrieb gavinreid@pseudocoder.co.uk:
>> As requested
>>
>> Exception in thread "main" java.io.IOException: 256 bit key length
>> is not supported yet for public key security
>> at
>> org.apache.pdfbox.pdmodel.encryption.PublicKeySecurityHandler.prepareDocumentForEncryption(PublicKeySecurityHandler.java:286)
>> at org.apache.pdfbox.pdfwriter.COSWriter.write(COSWriter.java:1313)
>> at org.apache.pdfbox.pdfwriter.COSWriter.write(COSWriter.java:1262)
>> at org.apache.pdfbox.pdmodel.PDDocument.save(PDDocument.java:1335)
>>
>> public static void main(String args[]) throws Exception {
>> PDDocument doc = PDDocument.load(new File("Resources/sample.pdf"));
>>
>> PublicKeyProtectionPolicy policy = new PublicKeyProtectionPolicy();
>> PublicKeyRecipient recip = new PublicKeyRecipient();
>> AccessPermission ap = new AccessPermission();
>> ap.setCanModify(false);
>> recip.setPermission(ap);
>> InputStream inStream = new
>> FileInputStream("Resources/CertExchange.cer");
>> CertificateFactory cf = CertificateFactory.getInstance("X.509");
>> InputStream is =
>> Files.newInputStream(Paths.get("Resources/keystore.pem"));
>> String keyStorePassword = "123456";
>> KeyStore keyStore = KeyStore.getInstance(KeyStore.getDefaultType());
>> keyStore.load(is, keyStorePassword.toCharArray());
>> X509Certificate certificate = (X509Certificate)
>> keyStore.getCertificate("Gavin");
>>
>> recip.setX509(certificate); // set the recipient's certificate
>> policy.addRecipient(recip);
>> policy.setEncryptionKeyLength(256); // the document will be
>> encrypted with 128 bits secret key
>> doc.protect(policy);
>> doc.save(new FileOutputStream("Resources/output.pdf"));
>>
>> }
>>
>>
>>
>> Quoting Tilman Hausherr <TH...@t-online.de>:
>>
>>> Hi,
>>> Please provide a stack trace and a working example, i.e. code and
>>> a certificate. Please upload these somewhere, attachments are
>>> usually deleted by the mailing list software.
>>> Tilman
>>>
>>> Am 21.12.2018 um 10:09 schrieb gavinreid@pseudocoder.co.uk:
>>>>
>>>> I'm using PDFBox 2.0.12 and I’m attempting to encrypt a PDF
>>>> Document using 256 bit keylength.
>>>>
>>>> But I’m receiving an Error that this is not supported, but it
>>>> appears that from the documentation that 256 IS supported but
>>>> only for passwords.
>>>>
>>>> Is there a mechanism for using the current working implementation
>>>> of passwords with the Certificate encryption?
>>>> (or any plans to allow 256 with certificates?)
>>>>
>>>> Regards
>>>>
>>>> Gavin
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>
---------------------------------------------------------------------
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>.
Hi,
Now I get it... I had a look at the code, we do not support AES at all
for public keys. Passing an 128 bit key results in a 128-Bit RC4
encryption LOL.
I've created an issue for this:
https://jira.apache.org/jira/browse/PDFBOX-4413
Please register and click to watch the issue.
I suspect that much of it is already available in the base class, but
PublicKeySecurityHandler.prepareDocumentForEncryption() is definitively
old stuff.
Tilman
Am 21.12.2018 um 10:29 schrieb gavinreid@pseudocoder.co.uk:
> As requested
>
> Exception in thread "main" java.io.IOException: 256 bit key length is
> not supported yet for public key security
> at
> org.apache.pdfbox.pdmodel.encryption.PublicKeySecurityHandler.prepareDocumentForEncryption(PublicKeySecurityHandler.java:286)
> at org.apache.pdfbox.pdfwriter.COSWriter.write(COSWriter.java:1313)
> at org.apache.pdfbox.pdfwriter.COSWriter.write(COSWriter.java:1262)
> at org.apache.pdfbox.pdmodel.PDDocument.save(PDDocument.java:1335)
>
> public static void main(String args[]) throws Exception {
> PDDocument doc = PDDocument.load(new
> File("Resources/sample.pdf"));
>
> PublicKeyProtectionPolicy policy = new
> PublicKeyProtectionPolicy();
> PublicKeyRecipient recip = new PublicKeyRecipient();
> AccessPermission ap = new AccessPermission();
> ap.setCanModify(false);
> recip.setPermission(ap);
> InputStream inStream = new
> FileInputStream("Resources/CertExchange.cer");
> CertificateFactory cf = CertificateFactory.getInstance("X.509");
> InputStream is =
> Files.newInputStream(Paths.get("Resources/keystore.pem"));
> String keyStorePassword = "123456";
> KeyStore keyStore =
> KeyStore.getInstance(KeyStore.getDefaultType());
> keyStore.load(is, keyStorePassword.toCharArray());
> X509Certificate certificate = (X509Certificate)
> keyStore.getCertificate("Gavin");
>
> recip.setX509(certificate); // set the recipient's certificate
> policy.addRecipient(recip);
> policy.setEncryptionKeyLength(256); // the document will be
> encrypted with 128 bits secret key
> doc.protect(policy);
> doc.save(new FileOutputStream("Resources/output.pdf"));
>
> }
>
>
>
> Quoting Tilman Hausherr <TH...@t-online.de>:
>
>> Hi,
>> Please provide a stack trace and a working example, i.e. code and a
>> certificate. Please upload these somewhere, attachments are usually
>> deleted by the mailing list software.
>> Tilman
>>
>> Am 21.12.2018 um 10:09 schrieb gavinreid@pseudocoder.co.uk:
>>>
>>> I'm using PDFBox 2.0.12 and I’m attempting to encrypt a PDF Document
>>> using 256 bit keylength.
>>>
>>> But I’m receiving an Error that this is not supported, but it
>>> appears that from the documentation that 256 IS supported but only
>>> for passwords.
>>>
>>> Is there a mechanism for using the current working implementation of
>>> passwords with the Certificate encryption?
>>> (or any plans to allow 256 with certificates?)
>>>
>>> Regards
>>>
>>> Gavin
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
Re: Certifcate Based AES256
Posted by ga...@pseudocoder.co.uk.
As requested
Exception in thread "main" java.io.IOException: 256 bit key length is
not supported yet for public key security
at
org.apache.pdfbox.pdmodel.encryption.PublicKeySecurityHandler.prepareDocumentForEncryption(PublicKeySecurityHandler.java:286)
at org.apache.pdfbox.pdfwriter.COSWriter.write(COSWriter.java:1313)
at org.apache.pdfbox.pdfwriter.COSWriter.write(COSWriter.java:1262)
at org.apache.pdfbox.pdmodel.PDDocument.save(PDDocument.java:1335)
public static void main(String args[]) throws Exception {
PDDocument doc = PDDocument.load(new File("Resources/sample.pdf"));
PublicKeyProtectionPolicy policy = new PublicKeyProtectionPolicy();
PublicKeyRecipient recip = new PublicKeyRecipient();
AccessPermission ap = new AccessPermission();
ap.setCanModify(false);
recip.setPermission(ap);
InputStream inStream = new
FileInputStream("Resources/CertExchange.cer");
CertificateFactory cf = CertificateFactory.getInstance("X.509");
InputStream is =
Files.newInputStream(Paths.get("Resources/keystore.pem"));
String keyStorePassword = "123456";
KeyStore keyStore = KeyStore.getInstance(KeyStore.getDefaultType());
keyStore.load(is, keyStorePassword.toCharArray());
X509Certificate certificate = (X509Certificate)
keyStore.getCertificate("Gavin");
recip.setX509(certificate); // set the recipient's certificate
policy.addRecipient(recip);
policy.setEncryptionKeyLength(256); // the document will be
encrypted with 128 bits secret key
doc.protect(policy);
doc.save(new FileOutputStream("Resources/output.pdf"));
}
Quoting Tilman Hausherr <TH...@t-online.de>:
> Hi,
> Please provide a stack trace and a working example, i.e. code and a
> certificate. Please upload these somewhere, attachments are usually
> deleted by the mailing list software.
> Tilman
>
> Am 21.12.2018 um 10:09 schrieb gavinreid@pseudocoder.co.uk:
>>
>> I'm using PDFBox 2.0.12 and I’m attempting to encrypt a PDF
>> Document using 256 bit keylength.
>>
>> But I’m receiving an Error that this is not supported, but it
>> appears that from the documentation that 256 IS supported but only
>> for passwords.
>>
>> Is there a mechanism for using the current working implementation
>> of passwords with the Certificate encryption?
>> (or any plans to allow 256 with certificates?)
>>
>> Regards
>>
>> Gavin
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
Re: Certifcate Based AES256
Posted by Tilman Hausherr <TH...@t-online.de>.
Hi,
Please provide a stack trace and a working example, i.e. code and a
certificate. Please upload these somewhere, attachments are usually
deleted by the mailing list software.
Tilman
Am 21.12.2018 um 10:09 schrieb gavinreid@pseudocoder.co.uk:
>
> I'm using PDFBox 2.0.12 and I’m attempting to encrypt a PDF Document
> using 256 bit keylength.
>
> But I’m receiving an Error that this is not supported, but it appears
> that from the documentation that 256 IS supported but only for passwords.
>
> Is there a mechanism for using the current working implementation of
> passwords with the Certificate encryption?
> (or any plans to allow 256 with certificates?)
>
> Regards
>
> Gavin
>
>
>
> ---------------------------------------------------------------------
> 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