)]}'
{
  "commit": "bbbb76d46b8ea934fdec9f2ed0ebd49a923496d4",
  "tree": "78f38a00bab8d5ea859e55c79da16dec3443172e",
  "parents": [
    "9868358cfaac0bc92ec6ae38d9727d0db4c26c65"
  ],
  "author": {
    "name": "Charles Duffy",
    "email": "chaduffy@cisco.com",
    "time": "Tue Sep 20 11:42:02 2016 -0500"
  },
  "committer": {
    "name": "Carlos Sanchez",
    "email": "carlos@apache.org",
    "time": "Mon Sep 26 17:03:10 2016 +0200"
  },
  "message": "Avoid eval, shell-injection via JAVA_OPTS or JENKINS_OPTS\n\nThe intent of using eval when processing JAVA_OPTS or JENKINS_OPTS is to allow arguments with spaces to be passed through and parsed without the bugs given in [BashFAQ #50](http://mywiki.wooledge.org/BashFAQ/050). By using `eval`, however, the issues discussed in [BashFAQ #48](http://mywiki.wooledge.org/BashFAQ/048) are introduced.\n\nStrings containing whitespace can be safely processed with `xargs`, which -- when not used with the non-POSIX extensions `-0` or `-d` -- follows shell quoting conventions in splitting its input stream into arguments.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "206e069f2141dd86b0659026b09c97f4a2675ebf",
      "old_mode": 33261,
      "old_path": "jenkins.sh",
      "new_id": "c8ad80f9c6bc202e8509c9471fdb3405ff276d75",
      "new_mode": 33261,
      "new_path": "jenkins.sh"
    }
  ]
}