Re: [PATCH] Pluggable disk formats for vmd (qcow2 preparation)

2018-08-15 Thread Ori Bernstein
Updated version below. This change fixes a few things: - Removes a 30 second sleep that I'd forgotten to remove while debugging. - Removes a dead seek() call. --- usr.sbin/vmd/Makefile | 2 +- usr.sbin/vmd/vioraw.c | 68 ++

Re: nologin(8): write -> dprintf

2018-08-15 Thread Alexander Hall
On August 15, 2018 4:27:24 PM GMT+02:00, Scott Cheloha wrote: >Use dprintf for the DEFAULT_MESG string instead of the more awkward >write+strlen combo. > >ok? > >-- >Scott Cheloha > >Index: sbin/nologin/nologin.c >=== >RCS file:

ubcmtp: fix multi-finger on type4 devices, pass in proper pressure

2018-08-15 Thread joshua stein
Type 4 devices like the MacBookPro12,1 have extra padding in between each chunk of finger data that needs to be skipped, otherwise the offset will be wrong and each additional finger will read as static coordinates. This must have been overlooked when it was added to the driver in 2015 since

arm64 intruction cache flushing and gdb

2018-08-15 Thread Mark Kettenis
ARMv8 (like ARMv7) does not guarantee coherence between the instruction and data caches. After writing data to memory that contains executable instructions, cache maintenance (flush, invalidate) is needed. The arm64 pmap implements this, but only for the case where the address space that needs

Re: nologin(8): write -> dprintf

2018-08-15 Thread Theo de Raadt
Todd C. Miller wrote: > > Use dprintf for the DEFAULT_MESG string instead of the more awkward > > write+strlen combo. > > I don't object to this but I also wouldn't object to rewriting > nologin.c to use stdio. I wonder if nologin was written in this ignore-errors-from-write style, such that

Re: nologin(8): write -> dprintf

2018-08-15 Thread Todd C. Miller
On Wed, 15 Aug 2018 09:27:24 -0500, Scott Cheloha wrote: > Use dprintf for the DEFAULT_MESG string instead of the more awkward > write+strlen combo. I don't object to this but I also wouldn't object to rewriting nologin.c to use stdio. - todd

Re: umsm(4) and umb(4) separate loading for the same composite USB modem device

2018-08-15 Thread Mark Kettenis
> Date: Wed, 15 Aug 2018 09:56:50 +0100 > From: Stuart Henderson > > On 2018/08/14 18:43, Bryan Vyhmeister wrote: > > On Tue, Aug 14, 2018 at 05:53:43PM +0300, Denis wrote: > > > Most of modern modems have serial discipline ports and USB Mobile > > > Broadband Interface Model (MBIM) interface in

nologin(8): write -> dprintf

2018-08-15 Thread Scott Cheloha
Use dprintf for the DEFAULT_MESG string instead of the more awkward write+strlen combo. ok? -- Scott Cheloha Index: sbin/nologin/nologin.c === RCS file: /cvs/src/sbin/nologin/nologin.c,v retrieving revision 1.7 diff -u -p -r1.7

Re: umsm(4) and umb(4) separate loading for the same composite USB modem device

2018-08-15 Thread Denis
umsm(4) patch is needed to recognize MC7304 by umsm(4) and to have both NMEA and AT ports enabled. Especially, I'm using MC7304's (MC7455 on another platform) NMEA port for NTP time corrections from GLO/GPS. AT port is needed for mode changes by AT commands. Very useful. umb(4) is a good one for

Re: CVE-2018-3615, CVE-2018-3620, CVE-2018-3646

2018-08-15 Thread Shawn Webb
On Wed, Aug 15, 2018 at 12:31:16AM -0600, Theo de Raadt wrote: > We had some idea this class of problem was coming, through hints we > received from others and an extremely cynical perspective that has > developed. We believe Intel cpus do almost no security checks up-front, > but defer checks

vmd send nameserver only once

2018-08-15 Thread Martijn van Duren
When running vmd with a local interface it sends the nameservers twice, which seems a bit redundant to me and always annoys me when editing resolv.conf manually inside the vm. Diff below removes one of the two instances. OK? martijn@ Index: dhcp.c

Re: nsd 4.1.24

2018-08-15 Thread Paul de Weerd
On Wed, Aug 15, 2018 at 03:12:19PM +0200, Florian Obser wrote: | When this goes in I think we should switch the default control socket | and stop listening on localhost. This makes a lot of sense to me, please make the UDS the default control socket. Thanks Florian! Paul | OK? | | diff --git

Re: inteldrm(4) regression from 6.1 to 6.2: wrong console resolution

2018-08-15 Thread Mark Kettenis
> Date: Wed, 15 Aug 2018 01:50:58 -0400 > From: Philippe Meunier > > Philippe Meunier wrote: > >Mark Kettenis wrote: > >>Does the diff below fix things? > > > >Yes, it fixes the console resolution problem, although a bunch of "vblank > >wait timed out on crtc 0" messages now show up (see dmesg's

Re: nsd 4.1.24

2018-08-15 Thread Florian Obser
When this goes in I think we should switch the default control socket and stop listening on localhost. OK? diff --git etc/nsd.conf etc/nsd.conf index 729a5f620ba..94710bfa5ae 100644 --- etc/nsd.conf +++ etc/nsd.conf @@ -19,6 +19,7 @@ server: remote-control: control-enable: yes +

nsd 4.1.24

2018-08-15 Thread Florian Obser
Now with systemd support! A more useful feature for us might be that nsd-control can now commuicate over a unix domain socket. OK? diff --git config.h.in config.h.in index d3470836f26..eded09dd6b3 100644 --- config.h.in +++ config.h.in @@ -317,6 +317,9 @@ /* Define to 1 if you have the

Re: umsm(4) and umb(4) separate loading for the same composite USB modem device

2018-08-15 Thread Stuart Henderson
On 2018/08/15 09:56, Stuart Henderson wrote: > On 2018/08/14 18:43, Bryan Vyhmeister wrote: > > On Tue, Aug 14, 2018 at 05:53:43PM +0300, Denis wrote: > > > Most of modern modems have serial discipline ports and USB Mobile > > > Broadband Interface Model (MBIM) interface in some port compositions

Re: umsm(4) and umb(4) separate loading for the same composite USB modem device

2018-08-15 Thread Stuart Henderson
On 2018/08/14 18:43, Bryan Vyhmeister wrote: > On Tue, Aug 14, 2018 at 05:53:43PM +0300, Denis wrote: > > Most of modern modems have serial discipline ports and USB Mobile > > Broadband Interface Model (MBIM) interface in some port compositions > > simultaneously. It seems very useful to have

CVE-2018-3615, CVE-2018-3620, CVE-2018-3646

2018-08-15 Thread Theo de Raadt
These 3 issues all relate to a bug in Intel cpus The cpu will speculatively honour invalid PTE against data in the on-core L1 cache. Memory disclosure occurs into the wrong context. These 3 issues (CVE-2018-3615, CVE-2018-3620, CVE-2018-3646) together are the currently public artifacts of this