)]}'
{
  "commit": "9ca898fff81b2cd5adeb77cf1795b4fe8ab07f7f",
  "tree": "efb83c4e1fa26b00e79d09d552ac3e54f61ae163",
  "parents": [
    "744677aaf516e2af60647297db6c0fe2e17cf330"
  ],
  "author": {
    "name": "Nick Kralevich",
    "email": "nnk@google.com",
    "time": "Thu Apr 04 10:10:01 2019 -0700"
  },
  "committer": {
    "name": "Nick Kralevich",
    "email": "nnk@google.com",
    "time": "Thu Apr 04 10:15:25 2019 -0700"
  },
  "message": "Avoid leaking property values into logs on error\n\nThe purpose of having fine grain read/write control over the property\nspace is to help ensure the confidentiality of data stored in\nproperties. Leaking property values into the dmesg buffer on errors\nexposes the value outside of the access control rules specified by\npolicy.\n\n(arguably this is also true for the property name, not just the value.\nHowever, property names are exposed in other places now, so the\nincentive to fix this is lower. It would also take away a valuable\ndebugging tool.)\n\nTest: compiles\nChange-Id: I4a0634b8b5e4fd2edf718eaf7343940df627366d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fc5538c51a1d6c5526cbc59ee6c038a1c98f48c9",
      "old_mode": 33188,
      "old_path": "init/property_service.cpp",
      "new_id": "467568c78a48ef90354ed8da97e7b4fbab0baf99",
      "new_mode": 33188,
      "new_path": "init/property_service.cpp"
    }
  ]
}