)]}'
{
  "commit": "3b381c32fc2c325cc4ffb9f9f30a7e96e9bd87c6",
  "tree": "b4eb46f5fe28b4734723c9ff4227a94a5bd32b4e",
  "parents": [
    "e96b312150d8e376c1ef463793d1929eca3618d5"
  ],
  "author": {
    "name": "Avneesh Sachdev",
    "email": "avneesh@opensourcerouting.org",
    "time": "Sun Feb 19 10:19:52 2012 -0800"
  },
  "committer": {
    "name": "Avneesh Sachdev",
    "email": "avneesh@opensourcerouting.org",
    "time": "Sun Apr 08 13:46:29 2012 -0700"
  },
  "message": "bgpd: fix issue in capability negotiation (BZ#700)\n\nAddress problem where bgpd would reject a session if a peer sent some\ncapabilities in its Open message, but did not include a Multiprotocol\nextensions capability. Note that the session would come up if there\nwere no capabilities at all in the Open message.\n\n  * Add the \u0027mp_capability\u0027 out parameter to\n    bgp_capability_parse(). Set it to \u00271\u0027 if a Multiprotocol\n    extensions capability is encountered.\n\n  * Switch on \u0027mp_capability\u0027 instead of \u0027capability\u0027 in the calling\n    functions to determine if the peer indicated the set of AFI/SAFIs\n    it supports.\n\n    The net result is that when a peer does not send an MP capability,\n    it is assumed to support the AFI/SAFIs configured for it locally.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b5b50bb5fa39ea1812476088736ddef6638e7b94",
      "old_mode": 33188,
      "old_path": "bgpd/bgp_open.c",
      "new_id": "0326d01bc72a8bbdc474f2af128edeeddb802b82",
      "new_mode": 33188,
      "new_path": "bgpd/bgp_open.c"
    },
    {
      "type": "modify",
      "old_id": "5d8087a8e520ad78f1cc9de0e51148124c21b2f1",
      "old_mode": 33188,
      "old_path": "bgpd/bgp_packet.c",
      "new_id": "390b556356d4b2ac158194d7d040f120bf1488d6",
      "new_mode": 33188,
      "new_path": "bgpd/bgp_packet.c"
    }
  ]
}