{"push_id":921804668,"size":2,"distinct_size":1,"ref":"refs/heads/hardened/current/master","head":"b146bb03954e3ef0c120542679a30b810cf3cc14","before":"181da2aeaa62141ba2793413e57f2e64e06a477e","commits":[{"sha":"31d78f6810b70b03dcf590bdcd1f8520d199099d","author":{"email":"b8dc8f2cdfce0fe79e39c0797e0ab03724501f95@FreeBSD.org","name":"melifaro"},"message":"Add rib_lookup_info() to provide API for retrieving individual route\n  entries data in unified format.\n\nThere are control plane functions that require information other than\n  just next-hop data (e.g. individual rtentry fields like flags or\n  prefix/mask). Given that the goal is to avoid rte reference/refcounting,\n  re-use rt_addrinfo structure to store most rte fields. If caller wants\n  to retrieve key/mask or gateway (which are sockaddrs and are allocated\n  separately), it needs to provide sufficient-sized sockaddrs structures\n  w/ ther pointers saved in passed rt_addrinfo.\n\nConvert:\n  * lltable new records checks (in_lltable_rtcheck(),\n    nd6_is_new_addr_neighbor().\n  * rtsock pre-add/change route check.\n  * IPv6 NS ND-proxy check (RADIX_MPATH code was eliminated because\n     1) we don't support RTF_ANNOUNCE ND-proxy for networks and there should\n       not be multiple host routes for such hosts 2) if we have multiple\n       routes we should inspect them (which is not done). 3) the entire idea\n       of abusing KRT as storage for ND proxy seems odd. Userland programs\n       should be used for that purpose).","distinct":false,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/31d78f6810b70b03dcf590bdcd1f8520d199099d"},{"sha":"b146bb03954e3ef0c120542679a30b810cf3cc14","author":{"email":"b0125fa187132d47dbe983b53b8ad9c1146edd9c@hardenedbsd.org","name":"Oliver Pinter +"},"message":"Merge remote-tracking branch 'freebsd/master' into hardened/current/master","distinct":true,"url":"https://api.github.com/repos/HardenedBSD/hardenedBSD/commits/b146bb03954e3ef0c120542679a30b810cf3cc14"}]}