I've been looking at the strong crypto side of it. I have a test file but the 
published spec is vague at times (unless you are in windows and can use their 
crypto library), not a huge hurdle but I've been busy. I should at least submit 
a patch that recognizes the four addl block types even if we don't do anything 
with them. ( I do NOT want to peek at other implementations. Cleanroom all the 
way.)

What are the license issues? I had looked at the legal stuff briefly but could 
have easily overlooked it since I was only looking at the tech note that 
documents their numerous versions.

Bear


Sent from my iPad

> On Nov 29, 2013, at 12:57 AM, Stefan Bodewig <bode...@apache.org> wrote:
> 
>> On 2013-11-29, dam6923 . wrote:
>> 
>> Is there any policy in place or method already laid out for putting
>> bounties on certain task items?  In particular, I could chip something
>> in for the following two tickets:
> 
> What Phil said.
> 
>> 1) https://issues.apache.org/jira/browse/COMPRESS-88
>> 2) https://issues.apache.org/jira/browse/COMPRESS-238
> 
> Note that COMPRESS-88 is extremely unlikely to end up in an official ASF
> distribution anyway - the real problem is PKWARE's licensing of the
> encryption parts of the spec.  This is unless you mean the WinZIP AES
> implementation or the "old encryption" rather than the strong crypto
> protocol described by PKWARE.
> 
> What Compress can do is provide hooks that an implementation of
> COMPRESS-88 can be maintained outside of Compress.  I plan to seriously
> get the ball rolling for Compress 2.x (which should provide said hooks
> in the ZIP package) after christmas but have too much on my plate to
> drive this right now.
> 
> Stefan
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to