{"push_id":879957122,"size":1,"distinct_size":1,"ref":"refs/heads/REL9_5_STABLE","head":"55a2cc844216838d743cae7d94bd4f38acc62d1e","before":"b17dbf26293e3805b5f7ab5a11a8e3f984c476ad","commits":[{"sha":"55a2cc844216838d743cae7d94bd4f38acc62d1e","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Be more paranoid about null return values from libpq status functions.\n\nPQhost() can return NULL in non-error situations, namely when a Unix-socket\nconnection has been selected by default.  That behavior is a tad debatable\nperhaps, but for the moment we should make sure that psql copes with it.\nUnfortunately, do_connect() failed to: it could pass a NULL pointer to\nstrcmp(), resulting in crashes on most platforms.  This was reported as a\nsecurity issue by ChenQin of Topsec Security Team, but the consensus of\nthe security list is that it's just a garden-variety bug with no security\nimplications.\n\nFor paranoia's sake, I made the keep_password test not trust PQuser or\nPQport either, even though I believe those will never return NULL given\na valid PGconn.\n\nBack-patch to all supported branches.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/55a2cc844216838d743cae7d94bd4f38acc62d1e"}]}