wireguard-openbsd/sbin/ipsecctl/parse.y, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sbin/ipsecctl/parse.y?h=jd%2Fqueueboosts 2020-02-07T13:01:34Z Extend the ipsecctl(8) parser to set the udpencap flag and port 2020-02-07T13:01:34Z bluhm bluhm@openbsd.org 2020-02-07T13:01:34Z urn:sha1:a3b4c2abd806f43bf603f8f0086c568ea77dc3d0 number of an SA. This will be useful to test IPsec with NAT-T. OK sthen@ tobhe@ Fix file descriptor leak due to popfile() never closing the main config file. 2019-08-26T18:53:58Z tobhe tobhe@openbsd.org 2019-08-26T18:53:58Z urn:sha1:da1e1ceac58e972f1471c3c499f362dc1e1435e7 The fix is the same as for other parse.y files in the tree (see bgpd(8) or unwind(8)) ok bluhm@ (unsigned) means (unsigned int) which on ptrdiff_t or size_t or other 2019-02-13T22:57:07Z deraadt deraadt@openbsd.org 2019-02-13T22:57:07Z urn:sha1:915c3f33d30399505d94a06fc5123e4bbdc9531f larger types really is a range reduction... Almost any cast to (unsigned) is a bug. ok millert tb benno sync cmdline_symset() changes with src/usr.sbin; OK sashan@ claudio@ 2018-11-07T08:10:45Z miko miko@openbsd.org 2018-11-07T08:10:45Z urn:sha1:22023c0153bbdc441c179488f6e8840d83abf7d6 - odd condition/test in PF lexer 2018-11-01T00:18:44Z sashan sashan@openbsd.org 2018-11-01T00:18:44Z urn:sha1:a1533359581417afa5cac550127d8aa8920ae72a (and other lexers too) This commit rectifies earlier change: in the lex... even inside quotes, a \ followed by space or tab should expand to space or tab, and a \ followed by newline should be ignored (as a line continuation). compatible with the needs of hoststated (which has the most strict quoted string requirements), and ifstated (where one commonly does line continuations in strings). OK deraadt@, OK millert@ Do for most running out of memory err() what was done for most running 2018-07-11T07:39:22Z krw krw@openbsd.org 2018-07-11T07:39:22Z urn:sha1:a062aa9d6a1c6c36ba1886ff476a56da7d9bd5de out of memory log_warn(). i.e. ("%s", __func__) instead of manual function names and redundant verbiage about which wrapper detected the out of memory condition. ok henning@ No need to mention which memory allocation entry point failed (malloc, 2018-07-09T12:05:10Z krw krw@openbsd.org 2018-07-09T12:05:10Z urn:sha1:6a3d55f939083b5d9457342b25519eade91f9c38 calloc or strdup), we just need to log that we ran out of memory in a particular function. Recommended by florian@ and deraadt@ ok benno@ henning@ tb@ Be consistent in warn() and log_warn() usage when 2018-07-08T17:15:07Z krw krw@openbsd.org 2018-07-08T17:15:07Z urn:sha1:3c12ada049ec8174546d7ebd54606e5a13c3e487 running out of memory. Next step, be correct *and* consistent. ok dennis@ tb@ benno@ schwarze@ Plug leak in error case of the common 'varset' implementations. 2018-04-26T14:12:19Z krw krw@openbsd.org 2018-04-26T14:12:19Z urn:sha1:16a0a9064f4764345d45428585eeceb3fe50c4e9 ok benno@ Support DH groups 19 to 21 and 25 to 30, just like iked(8) does. 2017-10-27T08:29:32Z mpi mpi@openbsd.org 2017-10-27T08:29:32Z urn:sha1:26c588cc18e0ac59a6019c7d831ab03bb591779c ok visa@, markus@