You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Adam Nichols (JIRA)" <ji...@apache.org> on 2009/09/11 21:22:58 UTC

[jira] Created: (PDFBOX-526) Add ability to read encrypted file & write unencrypted flie

Add ability to read encrypted file & write unencrypted flie
-----------------------------------------------------------

                 Key: PDFBOX-526
                 URL: https://issues.apache.org/jira/browse/PDFBOX-526
             Project: PDFBox
          Issue Type: New Feature
          Components: PDModel, Writing
    Affects Versions: 0.8.0-incubator
            Reporter: Adam Nichols


Currently, the COSWriter determines whether or not to use encryption, which makes sense, however there's no way to tell it you don't want to use encryption.  So if you open an encrypted document, there's no way to write out an unencrypted document (you can write out a document without a password, but it'll still be encrypted).  This means that encrypted documents can't be merged even if the password is known.

I have a patch which will allow writing out unencrypted documents.  By default it'll work as it did before, but there's a new function which can be called to mark the document to be written out with no protection.  I'll upload the patch soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (PDFBOX-526) Add ability to read encrypted file & write unencrypted flie

Posted by "Adam Nichols (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PDFBOX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772556#action_12772556 ] 

Adam Nichols commented on PDFBOX-526:
-------------------------------------

Can this be included in the 1.0.0 release?

> Add ability to read encrypted file & write unencrypted flie
> -----------------------------------------------------------
>
>                 Key: PDFBOX-526
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-526
>             Project: PDFBox
>          Issue Type: New Feature
>          Components: PDModel, Writing
>    Affects Versions: 0.8.0-incubator
>            Reporter: Adam Nichols
>         Attachments: write_unencrypted_docs_clean.patch
>
>
> Currently, the COSWriter determines whether or not to use encryption, which makes sense, however there's no way to tell it you don't want to use encryption.  So if you open an encrypted document, there's no way to write out an unencrypted document (you can write out a document without a password, but it'll still be encrypted).  This means that encrypted documents can't be merged even if the password is known.
> I have a patch which will allow writing out unencrypted documents.  By default it'll work as it did before, but there's a new function which can be called to mark the document to be written out with no protection.  I'll upload the patch soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (PDFBOX-526) Add ability to read encrypted file & write unencrypted flie

Posted by "Adam Nichols (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Nichols updated PDFBOX-526:
--------------------------------

    Attachment: write_unencrypted_docs.patch

This is a simple change which allows us to remove security / encryption on a document.

> Add ability to read encrypted file & write unencrypted flie
> -----------------------------------------------------------
>
>                 Key: PDFBOX-526
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-526
>             Project: PDFBox
>          Issue Type: New Feature
>          Components: PDModel, Writing
>    Affects Versions: 0.8.0-incubator
>            Reporter: Adam Nichols
>         Attachments: write_unencrypted_docs.patch
>
>
> Currently, the COSWriter determines whether or not to use encryption, which makes sense, however there's no way to tell it you don't want to use encryption.  So if you open an encrypted document, there's no way to write out an unencrypted document (you can write out a document without a password, but it'll still be encrypted).  This means that encrypted documents can't be merged even if the password is known.
> I have a patch which will allow writing out unencrypted documents.  By default it'll work as it did before, but there's a new function which can be called to mark the document to be written out with no protection.  I'll upload the patch soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (PDFBOX-526) Add ability to read encrypted file & write unencrypted flie

Posted by "Adam Nichols (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Nichols updated PDFBOX-526:
--------------------------------

    Attachment: write_unencrypted_docs_clean.patch

Same patch, but this one applies cleanly to the head tag.

> Add ability to read encrypted file & write unencrypted flie
> -----------------------------------------------------------
>
>                 Key: PDFBOX-526
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-526
>             Project: PDFBox
>          Issue Type: New Feature
>          Components: PDModel, Writing
>    Affects Versions: 0.8.0-incubator
>            Reporter: Adam Nichols
>         Attachments: write_unencrypted_docs.patch, write_unencrypted_docs_clean.patch
>
>
> Currently, the COSWriter determines whether or not to use encryption, which makes sense, however there's no way to tell it you don't want to use encryption.  So if you open an encrypted document, there's no way to write out an unencrypted document (you can write out a document without a password, but it'll still be encrypted).  This means that encrypted documents can't be merged even if the password is known.
> I have a patch which will allow writing out unencrypted documents.  By default it'll work as it did before, but there's a new function which can be called to mark the document to be written out with no protection.  I'll upload the patch soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (PDFBOX-526) Add ability to read encrypted file & write unencrypted flie

Posted by "Adam Nichols (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Nichols updated PDFBOX-526:
--------------------------------

    Attachment:     (was: write_unencrypted_docs.patch)

> Add ability to read encrypted file & write unencrypted flie
> -----------------------------------------------------------
>
>                 Key: PDFBOX-526
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-526
>             Project: PDFBox
>          Issue Type: New Feature
>          Components: PDModel, Writing
>    Affects Versions: 0.8.0-incubator
>            Reporter: Adam Nichols
>         Attachments: write_unencrypted_docs_clean.patch
>
>
> Currently, the COSWriter determines whether or not to use encryption, which makes sense, however there's no way to tell it you don't want to use encryption.  So if you open an encrypted document, there's no way to write out an unencrypted document (you can write out a document without a password, but it'll still be encrypted).  This means that encrypted documents can't be merged even if the password is known.
> I have a patch which will allow writing out unencrypted documents.  By default it'll work as it did before, but there's a new function which can be called to mark the document to be written out with no protection.  I'll upload the patch soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.