)]}'
{
  "commit": "027429a34fd229d7546640bd5b629156da8dd0fd",
  "tree": "898231a189fb42ae3b64299120e903e443d7d694",
  "parents": [
    "9690e2b370f3f303ef75e1fd5c7fdbea8787d46a"
  ],
  "author": {
    "name": "Alistair Strachan",
    "email": "alistair.strachan@imgtec.com",
    "time": "Wed Jul 17 10:41:49 2013 -0700"
  },
  "committer": {
    "name": "Doug Zongker",
    "email": "dougz@android.com",
    "time": "Mon Nov 18 09:52:46 2013 -0800"
  },
  "message": "Restore default umask after forking for update-binary.\n\nA system/core change made in Mar 26 2012 6ebf12f \"init: Change umask\nof forked processes to 077\" changed the default umask of services\nforked from init.\n\nBecause recovery is forked from init, it has a umask of 077. Therefore\nwhen update-binary is forked from recovery, it too has a umask of 077.\n\nThis umask is overly restrictive and can cause problems for scripts\nrelying on minzip to extract binaries directly into the target\nfilesystem. Any directories updated by minzip will have their\npermissions reset to r-x------ and created files will have similarly\nrestrictive permissions.\n\nAs it seems unlikely this security measure was intended to have this\nside effect on legacy sideloads that do not have chmods to repair\nthe damage done by minzip, this change reverts the umask to 022 in\nthe fork made for update-binary.\n\nChange-Id: Ib1a3fc83aa4ecc7480b5d0c00f3c7d0d040d4887\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "797a525fd4214208d5a3304e7c9261483527fa40",
      "old_mode": 33188,
      "old_path": "install.cpp",
      "new_id": "980830cc06690ca41261af87e622fe53534afac4",
      "new_mode": 33188,
      "new_path": "install.cpp"
    }
  ]
}