[jira] Created: (COMPRESS-98) Handle AES encryption gracefully

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (COMPRESS-98) Handle AES encryption gracefully

Gilles Sadowski (Jira)
Handle AES encryption gracefully
--------------------------------

                 Key: COMPRESS-98
                 URL: https://issues.apache.org/jira/browse/COMPRESS-98
             Project: Commons Compress
          Issue Type: Improvement
    Affects Versions: 1.0
            Reporter: Trejkaz


Currently, attempts to read an AES encrypted zip file results in "invalid compression method".  This different form of compression for whatever reason went with a compression type identifier to indicate its use.

Problem is when I get this error, the library doesn't tell me what compression method it tried to use - having a specific subclass of IOException that I can interrogate for the compression method it couldn't find would be very useful.

This is important to us because we value accuracy, and marking encrypted entries as unsupported is a change in semantics for our application.


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

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (COMPRESS-98) Handle AES encryption gracefully

Gilles Sadowski (Jira)

     [ https://issues.apache.org/jira/browse/COMPRESS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig resolved COMPRESS-98.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1

The title is a bit of a misnomer since there isn't anything graceful about throwing a specialized exception.  8-)

A new exception type has been added and gets used with svn revision 920808.


> Handle AES encryption gracefully
> --------------------------------
>
>                 Key: COMPRESS-98
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-98
>             Project: Commons Compress
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: Trejkaz
>             Fix For: 1.1
>
>
> Currently, attempts to read an AES encrypted zip file results in "invalid compression method".  This different form of compression for whatever reason went with a compression type identifier to indicate its use.
> Problem is when I get this error, the library doesn't tell me what compression method it tried to use - having a specific subclass of IOException that I can interrogate for the compression method it couldn't find would be very useful.
> This is important to us because we value accuracy, and marking encrypted entries as unsupported is a change in semantics for our application.

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