{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "",
    "ClosedDate": null,
    "CommentCount": 0,
    "Custom": null,
    "Description": "If you have a zip file with an AES-256 encrypted content file, and use the following trivial code to modify the zip comment, nothing apparently goes wrong.\n \nThe modified zip file can be opened, and the comment read back, but when you try to extract the encrypted content it's corrupt.\n \nThere's no such problem with ZipCrypto encrypted content.\n \nHere's all the code to repro the problem:\n \nstatic void Main( string[] args )\n{\n\tZipFile zip = new ZipFile( args[0] );\n\tzip.Comment = \"My Comment\";\n\tzip.Save();\n}\n \nThe corruption occurs on AES-256 encrypted content created with both WinZip and 7-zip.",
    "LastUpdatedDate": "2013-02-21T18:42:51.313-08:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2012-05-04T03:16:17.933-07:00",
    "Status": {
      "Name": "Proposed",
      "Id": 1
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "Trivial code to modify and save a zip corrupts AES encrypted content",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 2,
    "Id": 15123
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "Yes, I'm getting this and it is being a real pain as I need it to work (otherwise I have to find something else [or remove a feature from my product, which I don't want to do], and I don't think that is possible – this is a really great library, and one of very few for .NET).\r\n\r\nI was adding or updating a number of files, and found that the files that I had added/updated were fine, but no other files in the archive. When trying to read the other files into a stream with ZipEntry.Extract(), I would get a CRC error. It was expecting a CRC of 0x00000000, but calculated a normal CRC. When viewing it in PeaZip (uses 7-Zip for zip files, as far as I know), prior to modification with this, the CRC column was empty but afterwards it displayed 00000000.\r\n\r\nAs above, all it takes seems to be something that makes ZipFile.Save() run, and it doesn't happen with ZipCrypto or non-encrypted zips.\r\n\r\nHope this helps.",
      "PostedDate": "2012-05-17T22:35:51.563-07:00",
      "Id": -2147483648
    },
    {
      "Message": "Well, I have something else interesting to report on this: when creating an AES256 encrypted zip with this library rather than 7-Zip or WinZip, it can be edited without any corruption occurring. Which fortunately solves my problem!",
      "PostedDate": "2012-05-18T15:34:36.25-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:42:51.313-08:00",
      "Id": -2147483648
    }
  ]
}