{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "fixed in changeset 22534.  This behavior will be in v1.6. \nIt is in the preview v1.6 release now.",
    "ClosedDate": "2008-08-24T10:44:47.793-07:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "What does ExtractAll do when some entries in the archive have passwords? \nThe behavior should ideally be unsurprising, and documented. \nAlso, we need a set of tests for ExtractAll to verify that the documented behavior is the actual behavior.",
    "LastUpdatedDate": "2013-05-16T05:32:44.483-07:00",
    "PlannedForRelease": "1.6 DotNetZip Library",
    "ReleaseVisibleToPublic": true,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2008-06-07T09:43:30.663-07:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "Behavior for ExtractAll when Passwords are present.",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 5178
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "I fixed this in changeset 22534.  The behavior is now reasonable and documented. \r\nThere is one catch:  \r\nIf the zipfile contains entries that are encrypted with different passwords, then ExtractAll will not succeed.  \r\nThe app will need to supply the distinct passwords for the distinct entries, and that will require the application to use the individual Extract() methods.",
      "PostedDate": "2008-08-24T10:44:22.98-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2008-08-24T10:44:47.793-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:44:48.25-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-05-16T05:32:44.483-07:00",
      "Id": -2147483648
    }
  ]
}