[
https://issues.apache.org/jira/browse/PDFBOX-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908662#comment-14908662
]
Ben McCann commented on PDFBOX-1450:
------------------------------------
Just to confirm I'm understanding... I believe that we want to change "int
keyLength = 128;" to "int keyLength = 256;" on that page after 2.0 is released.
And that's what this bug is about, right?
What I was suggesting was that having Fix Version as 2.0.0 makes it look like
this needs to be fixed before 2.0 is released. I was trying to help inventory
what's left to do for a 2.0 release and see if there are any tasks I can help
with. Since we can't fix this until after 2.0 is released, I though maybe a
version number like 2.0.1 would make more sense to help clean up the list of
2.0 items. Or at least changing the title to "document how to encrypt with AES
256 after 2.0 is released" so that it's more immediately obvious that this
can't be worked on and doesn't block 2.0
> document how to encrypt with AES 256
> ------------------------------------
>
> Key: PDFBOX-1450
> URL: https://issues.apache.org/jira/browse/PDFBOX-1450
> Project: PDFBox
> Issue Type: Wish
> Components: Documentation
> Affects Versions: 2.0.0
> Reporter: Ralf Hauser
> Priority: Minor
> Fix For: 2.0.0
>
>
> please add a java code sample how to do this on the web-site and link to it
> from
> http://pdfbox.apache.org/commandlineutilities/Encrypt.html
> see also see also PDFBOX-953 and see also PDFBOX-135
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
