)]}'
{
  "commit": "0e4303d3173ecc264b3ec39a863174670bbe2900",
  "tree": "f525c8543f07581c9a87fcffb843537e87ddf820",
  "parents": [
    "f1ef81b2476ea533ac3d2129aa0e89653c427323"
  ],
  "author": {
    "name": "Roman Hoog Antink",
    "email": "rha@open.ch",
    "time": "Fri Jan 18 13:52:03 2013 +0100"
  },
  "committer": {
    "name": "David Lamparter",
    "email": "equinox@opensourcerouting.org",
    "time": "Sat Feb 23 18:22:34 2013 +0100"
  },
  "message": "bgpd: fix lost passwords of grouped neighbors\n\nThis patch resolves the significance of order of group and password\nstatements.\n\nIt prevents passwords from being lost in cases where all\nthree conditions apply:\n  1. the peer is member of a group with or without group password\n  2. the peer has an individual password set\n  3. the peer is added to a group within an address-family ipv6\n     section\n\nIn addition this patch prevents the same issue in cases, where an IPv4\npeer\u0027s password is set first and the peer is added to a group\nafterwards.\n\nAdding a peer to a group cancels his individual password. Without ipv6\nthis is not a problem, because choosing the right order of config\nstatements will do (set password only after adding peer to group).\n\nWhen adding the peer to a group within the address-family\nsection, his password is definitely lost. The same workaround (ie.\nsetting the password after the address-family section) can not be used,\nbecause \"show run\" will print the configuration statements in the wrong\norder.\n\nSigned-off-by: David Lamparter \u003cequinox@opensourcerouting.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0b3f0a8e9338a2030fa84c9d9e2708101c4d6062",
      "old_mode": 33188,
      "old_path": "bgpd/bgpd.c",
      "new_id": "c9a04fff9b4aa80b3635b1aeadd0ac1589ebcd39",
      "new_mode": 33188,
      "new_path": "bgpd/bgpd.c"
    }
  ]
}