CVS: cvs.openbsd.org: src

2019-10-18 Thread Stefan Sperling
CVSROOT:/cvs
Module name:src
Changes by: s...@cvs.openbsd.org2019/10/18 01:07:53

Modified files:
sys/dev/pci: if_iwm.c if_iwmreg.h if_iwmvar.h 

Log message:
Add support for dynamic queue allocation (DQA) to iwm(4).

Required for new firmware images because the command queue index has changed.
The driver remains compatible with our current firmware images for now.

Tested by benno, jan, kevlo, florian, jmatthew, Tracey Emery
ok jmatthew



CVS: cvs.openbsd.org: www

2019-10-18 Thread Anthony J . Bentley
CVSROOT:/cvs
Module name:www
Changes by: bent...@cvs.openbsd.org 2019/10/18 02:40:05

Modified files:
.  : 66.html 

Log message:
Fix some typos pointed out by Raf Czlonka.



CVS: cvs.openbsd.org: www

2019-10-18 Thread Ingo Schwarze
CVSROOT:/cvs
Module name:www
Changes by: schwa...@cvs.openbsd.org2019/10/18 09:22:29

Modified files:
.  : innovations.html 

Log message:
sysupgrade(8), snmp(1), rpki-client(8), and the ber API



CVS: cvs.openbsd.org: src

2019-10-18 Thread Ted Unangst
CVSROOT:/cvs
Module name:src
Changes by: t...@cvs.openbsd.org2019/10/18 11:14:08

Modified files:
lib/libc/gen   : login_cap.c 

Log message:
setting uid to -1 won't work with setresuid, so detect that condition
and return an error instead. may prevent some unset/missing confusion.
ok deraadt millert



CVS: cvs.openbsd.org: src

2019-10-18 Thread Ted Unangst
CVSROOT:/cvs
Module name:src
Changes by: t...@cvs.openbsd.org2019/10/18 11:15:45

Modified files:
usr.bin/doas   : doas.c 

Log message:
add some checks to avoid UID_MAX (-1) here. this is not problematic with
the current code, but it's probably safer this way.
ok deraadt



CVS: cvs.openbsd.org: src

2019-10-18 Thread Sebastian Benoit
CVSROOT:/cvs
Module name:src
Changes by: be...@cvs.openbsd.org   2019/10/18 12:35:32

Modified files:
sys/netinet6   : nd6_nbr.c 

Log message:
Don't check that the ipv6 source address of a neighbor advertisment is
from a neighbor's address. Sthen@ dug out RFC 4861 4.4 that says that
the source address is "An address assigned to the interface from which
the advertisement is sent." -- which can be from a network that the
receiver does not know about. Indeed my provider sends such a neighbor
advertisment for my default gateway, which breaks my uplink.

Claudio@ added this check for symetry with NetBSD code when he added
the same check to nd6_ns_input(), where it is needed to fix
CVE-2008-2476. See also OpenBSD 4.2 errata 15.

ok claudio@, kn@



Re: CVS: cvs.openbsd.org: src

2019-10-18 Thread Florian Obser
Welcome to the world of tomorrow!
Also, didn't we fix this ages ago?! I distinctly remember this coming up 
before...

On 18 October 2019 20:35:32 CEST, Sebastian Benoit  wrote:
>CVSROOT:   /cvs
>Module name:   src
>Changes by:be...@cvs.openbsd.org   2019/10/18 12:35:32
>
>Modified files:
>   sys/netinet6   : nd6_nbr.c 
>
>Log message:
>Don't check that the ipv6 source address of a neighbor advertisment is
>from a neighbor's address. Sthen@ dug out RFC 4861 4.4 that says that
>the source address is "An address assigned to the interface from which
>the advertisement is sent." -- which can be from a network that the
>receiver does not know about. Indeed my provider sends such a neighbor
>advertisment for my default gateway, which breaks my uplink.
>
>Claudio@ added this check for symetry with NetBSD code when he added
>the same check to nd6_ns_input(), where it is needed to fix
>CVE-2008-2476. See also OpenBSD 4.2 errata 15.
>
>ok claudio@, kn@

-- 
Sent from a mobile device. Please excuse poor formating.



CVS: cvs.openbsd.org: www

2019-10-18 Thread Brent Cook
CVSROOT:/cvs
Module name:www
Changes by: bc...@cvs.openbsd.org   2019/10/18 17:52:43

Modified files:
libressl   : index.html releases.html 

Log message:
LibreSSL 3.0.2



CVS: cvs.openbsd.org: src

2019-10-18 Thread Visa Hankala
CVSROOT:/cvs
Module name:src
Changes by: v...@cvs.openbsd.org2019/10/19 00:56:18

Modified files:
sys/miscfs/deadfs: dead_vnops.c 

Log message:
Unlock the vnode in vop_inactive of deadfs. The unlock operation is
a no-op at the moment, but future work will introduce an actual lock
that has to be released.

OK mpi@ anton@