)]}'
{
  "commit": "d830e565e704efc62c0b21d55ee35a035110e235",
  "tree": "c7fac44918e161de038cbd6a7848510576782f1b",
  "parents": [
    "afdd600c0982f0ce95439f2936c6d6d6d0201f77"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Thu Nov 16 15:20:10 2023 +0000"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Fri Apr 26 16:32:22 2024 +0100"
  },
  "message": "gdb: Add a SECURITY.txt document for GDB\n\nThis commit adds a SECURITY document to GDB.  The idea behind this\ndocument is to define what security expectations a user can reasonably\nhave when using GDB.  In addition the document specifies which bugs\nGDB developers consider a security bug, and which are just \"normal\"\nbugs.\n\nDiscussion for the creation of this initial version can be found here:\n\n  https://inbox.sourceware.org/gdb-patches/877cmvui64.fsf@redhat.com/\n\nLike any part of GDB, this is not intended as the absolute final\nversion, instead this is a living document, and this is just a\nreasonable starting point from which we can iterate.\n\nFor now I\u0027ve added this document as a text file but I am considering\nmerging this document into the manual at a later date, and having the\nSECURITY.txt file just say \"Read the manual\"\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "e483790349bf090550a1953c3b6543b04e76df9a",
      "new_mode": 33188,
      "new_path": "gdb/SECURITY.txt"
    }
  ]
}
