{"push_id":870215341,"size":7,"distinct_size":7,"ref":"refs/heads/master","head":"ea5482715a821541a3decdf511de0059775308ec","before":"9d8dacc238e1c3feeb557b8fca0f87269cd8b8ed","commits":[{"sha":"3459814a1aaef1283117a36d3a18775983049e26","author":{"email":"eea650d910a45d351f31d90f2ec0fd6b64ab3573@gmail.com","name":"doktornotor"},"message":"Use full path to executable in mwexec() call","distinct":true,"url":"https://api.github.com/repos/pfsense/pfsense/commits/3459814a1aaef1283117a36d3a18775983049e26"},{"sha":"9098719154388b85c6e0841223545e5c4ed19193","author":{"email":"eea650d910a45d351f31d90f2ec0fd6b64ab3573@gmail.com","name":"doktornotor"},"message":"interfaces.inc - use full paths to executables","distinct":true,"url":"https://api.github.com/repos/pfsense/pfsense/commits/9098719154388b85c6e0841223545e5c4ed19193"},{"sha":"84c82d3dbe280544f28e6288e7e447272b507ba8","author":{"email":"eea650d910a45d351f31d90f2ec0fd6b64ab3573@gmail.com","name":"doktornotor"},"message":"pfsense-utils.inc - use full paths to executables","distinct":true,"url":"https://api.github.com/repos/pfsense/pfsense/commits/84c82d3dbe280544f28e6288e7e447272b507ba8"},{"sha":"25118b25d2add05fe54e815bab4acc2317d4cbbd","author":{"email":"eea650d910a45d351f31d90f2ec0fd6b64ab3573@gmail.com","name":"doktornotor"},"message":"filter_log.inc - use full paths to executables","distinct":true,"url":"https://api.github.com/repos/pfsense/pfsense/commits/25118b25d2add05fe54e815bab4acc2317d4cbbd"},{"sha":"bcfe27479ac50d37e4c68ef5de60319655b5fd1b","author":{"email":"eea650d910a45d351f31d90f2ec0fd6b64ab3573@gmail.com","name":"doktornotor"},"message":"filter_log.inc - use full paths to executables","distinct":true,"url":"https://api.github.com/repos/pfsense/pfsense/commits/bcfe27479ac50d37e4c68ef5de60319655b5fd1b"},{"sha":"d08aeac11a9be8a89a85341515063e98eee1943f","author":{"email":"545605536038c5fc1fd68bbfa4d633a0a6400978@inf.org","name":"Phil Davis"},"message":"Fix tooltip text for associated filter rules\n\n1) Add a port forward with associated filter rule\r\n2) Go to firewall_rules and hover over the icon on the left of the rule.\r\nIt says \"traffic is ed\".\r\n\r\nThe problem is that, for whatever reason, an associated rule does not have ['type'] specified, even in config.xml. It is that way in 2.2.5, so not a new thing or regression. I guess that the back-end rule generation works by assuming that a rule in config.xml that does not have 'type' defined should be a pass rule.\r\n\r\nSo we can't write code anywhere that assumes that every rule has a defined 'type'.\r\n\r\nThis text was different fixed stuff in 2.2.5, so there was no problem there.\r\n\r\nIn fixing this I also made the text explicit for each type. This will help with the gettext translation. The way it did it before, putting \"ed\" on the end, would not have worked for translation.","distinct":true,"url":"https://api.github.com/repos/pfsense/pfsense/commits/d08aeac11a9be8a89a85341515063e98eee1943f"},{"sha":"ea5482715a821541a3decdf511de0059775308ec","author":{"email":"545605536038c5fc1fd68bbfa4d633a0a6400978@inf.org","name":"Phil Davis"},"message":"Make block bogon rule display consistent\n\nThe block private networks and anti-lockout rules display in the firewall rules display with the schedule column blank. But the block bogon networks has an asterisk. That looks odd. I noticed it just now when looking at firewall rules in 2.3 and looked back in 2.2.5 also - it is the same there.","distinct":true,"url":"https://api.github.com/repos/pfsense/pfsense/commits/ea5482715a821541a3decdf511de0059775308ec"}]}