{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "initially implemented in changeset 28766.  This will be in the next v1.7 preview release.",
    "ClosedDate": "2009-02-09T12:32:55.657-08:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "Would like to see strong encryption option.",
    "LastUpdatedDate": "2013-05-16T05:32:34.107-07:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "High",
      "Severity": 150,
      "Id": 3
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2008-12-19T11:33:02.147-08:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "Support AES 128 and 256",
    "Type": {
      "Name": "Feature",
      "Id": 1
    },
    "VoteCount": 4,
    "Id": 6834
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "Forgot to mention - awesome library!  Thanks for what you are doing on this project.",
      "PostedDate": "2008-12-19T11:34:20.193-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2008-12-19T12:57:46.803-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2009-01-13T09:15:32.877-08:00",
      "Id": -2147483648
    },
    {
      "Message": "Thanks for the comments.  Ok, here's a question.  There is a one AES encryption mechanism specified and used by WinZip, and there is another specified and used by PKWare.  Actually AES is just AES, but the different vendors specify different metadata around the encrypted data.  They result in different formatting of the zip file.  A zip created by WinZip that uses AES256 will not be readable by the PKWare SecureZip tool.   Which should I implement in DotNetZip? \r\n\r\nWhich is the one that people want? \r\n\r\nI could implement both.  I'm trying to think if this would overly complicate the interface.  I think it might be ok.  I'd need a new property on the ZipFile, to specify whether to use WinZip or PKWare's AES.  Developers would use the Encryption property on the ZipEntry to specify AES128 AES256, etc, but the formatting of the file is something different, and would need to be specified independently on an archive-wide basis.  I would need to do lots of testing. \r\n\r\nBut which is the one that people want FIRST? \r\nPlease comment here.  PKWare or WinZip ? \r\n\r\n\r\n\r\n",
      "PostedDate": "2009-01-14T06:09:12.42-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2009-01-14T08:39:18.143-08:00",
      "Id": -2147483648
    },
    {
      "Message": "Great library.  I actually have an immediate need for AES, so I'm voting for this. :)\r\n\r\nAs for which flavor of AES to implement, I have no idea.",
      "PostedDate": "2009-01-14T08:40:47.8-08:00",
      "Id": -2147483648
    },
    {
      "Message": "\"But which is the one that people want FIRST? \", it depends on which is more popular :)",
      "PostedDate": "2009-01-14T21:24:53.26-08:00",
      "Id": -2147483648
    },
    {
      "Message": "Yes, that's the thing - I have no idea what people are using now, so I don't know which one is preferred.   I guess I'll just pick one.",
      "PostedDate": "2009-01-15T11:34:44.673-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2009-01-19T06:56:31.557-08:00",
      "Id": -2147483648
    },
    {
      "Message": "Status update.  I picked WinZip's AES to focus on.   And, I just completed an initial proof-of-concept for AES support.  I have AES256 decryption working, with compatibility with WinZip files.  (For some reason I could not get AES128 to work properly?)   I do not yet have AES256 encryption working, and I do not have it all integrated with v1.7.  But it is a start.\r\n",
      "PostedDate": "2009-01-24T22:51:09.463-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2009-02-09T12:32:55.657-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:44:34.75-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-05-16T05:32:34.107-07:00",
      "Id": -2147483648
    }
  ]
}