The FreeBSD 12 code, released today, does recognize the eMMC drive
mmc0: on sdhci_pci0
mmcsd0: 31GB at mmc0
200.0MHz/8bit/8192-block
mmcsd0boot0: 4MB partion 1 at mmcsd0
mmcsd0boot1: 4MB partion 2 at mmcsd0
mmcsd0rpmb: 4MB partion 3 at mmcsd0
The drive was accessible by FreeBSD's
ok?
Index: kern/sysv_sem.c
===
RCS file: /cvs/src/sys/kern/sysv_sem.c,v
retrieving revision 1.53
diff -u -p -r1.53 sysv_sem.c
--- kern/sysv_sem.c 14 Mar 2015 03:38:50 - 1.53
+++ kern/sysv_sem.c 11 Dec 2018 16:36:20
ok?
Index: kern/sysv_shm.c
===
RCS file: /cvs/src/sys/kern/sysv_shm.c,v
retrieving revision 1.69
diff -u -p -r1.69 sysv_shm.c
--- kern/sysv_shm.c 15 Sep 2016 02:00:16 - 1.69
+++ kern/sysv_shm.c 11 Dec 2018 16:42:55
- Unify the two hooks by passing the same argument
- Check for nullity before dereferencing `if_bridgeport', this will
matter when we go MP
- Use the same pattern to find a member in the ioctl path
ok?
Index: net/if_bridge.c
===
Hi Brad,
Exciting to see you working on this. However, I'm afraid the
implementation you describe sounds deeply flawed and kind of misses
the point of WireGuard.
On Tue, Dec 11, 2018 at 2:24 PM wrote:
> Currently, I want to take all the code that doesn't need to be in the
> kernel and move it
Hi,
since the Xorg setuid bit was removed, I looked a little bit into what
it would take to run it without root privs. I have a proof of concept
put together, and things seem to work (on an X220 amd64 + modesetting
driver, inteldrm; login on ttyC0 and running xinit). Testing the waters
here to
On Tue, Dec 11, 2018 at 02:35:33PM -0700, Theo de Raadt wrote:
> Ted Unangst wrote:
>
> > Marc Espie wrote:
> > > > > - try to remove the files normally first
> > > > > rm -f ${SUDO_CLEAN} || test -z "${SUDO}" || ${SUDO} rm -f
> > > > > ${SUDO_CLEAN}
> > > > >
> > > > > this should
Marc Espie wrote:
> > > - try to remove the files normally first
> > > rm -f ${SUDO_CLEAN} || test -z "${SUDO}" || ${SUDO} rm -f
> > > ${SUDO_CLEAN}
> > >
> > > this should actually fix the issue.
> > >
> > > Any other directory with that problem ?
> >
> > that fix the issue and the
On Tue, Dec 11, 2018 at 04:27:19PM -0500, Ted Unangst wrote:
> Mark Kettenis wrote:
> > > From: "Ted Unangst"
> > > Date: Mon, 10 Dec 2018 14:14:08 -0500
> > > Content-Type: text/plain; charset=utf-8
> > >
> > > So I was actually looking at the passwd check rules because I wanted
> > > to add a
Ted Unangst [t...@tedunangst.com] wrote:
>
> i get tired of typing the same password five times.
The first three times, just hit 'a'
The fourth time, enter the password you want
Claudio Jeker wrote:
> I think the main issue is that /usr/sr/regress was not moved to the
> priv-drop security model. There is bunch of code which needs root but I
> don't want to run all of regress as user root.
regress is very special
On Tue, Dec 11, 2018 at 02:35:33PM -0700, Theo de Raadt wrote:
> Ted Unangst wrote:
>
> > Marc Espie wrote:
> > > > > - try to remove the files normally first
> > > > > rm -f ${SUDO_CLEAN} || test -z "${SUDO}" || ${SUDO} rm -f
> > > > > ${SUDO_CLEAN}
> > > > >
> > > > > this should
Marc Espie wrote:
> On Mon, Dec 10, 2018 at 01:33:49PM +0100, Solene Rapenne wrote:
> > hi
> >
> > I have SUDO=doas in /etc/mk.conf for ports, this is preventing a `make
> > build`
> > in /usr/src as root if /etc/doas.conf doesn't have a line "permit nopass
> > root
> > as root". This fails
On Tue, Dec 11, 2018 at 06:50:07PM +0100, Solene Rapenne wrote:
> Marc Espie wrote:
> > On Mon, Dec 10, 2018 at 01:33:49PM +0100, Solene Rapenne wrote:
> > > hi
> > >
> > > I have SUDO=doas in /etc/mk.conf for ports, this is preventing a `make
> > > build`
> > > in /usr/src as root if
> From: "Ted Unangst"
> Cc: tech@openbsd.org
> Date: Tue, 11 Dec 2018 16:27:19 -0500
> Content-Type: text/plain; charset=utf-8
>
> Mark Kettenis wrote:
> > > From: "Ted Unangst"
> > > Date: Mon, 10 Dec 2018 14:14:08 -0500
> > > Content-Type: text/plain; charset=utf-8
> > >
> > > So I was
Ted Unangst wrote:
> Marc Espie wrote:
> > > > - try to remove the files normally first
> > > > rm -f ${SUDO_CLEAN} || test -z "${SUDO}" || ${SUDO} rm -f
> > > > ${SUDO_CLEAN}
> > > >
> > > > this should actually fix the issue.
> > > >
> > > > Any other directory with that problem ?
> Date: Tue, 11 Dec 2018 22:39:37 +0100
> From: Antoine Jacoutot
>
> On Tue, Dec 11, 2018 at 04:27:19PM -0500, Ted Unangst wrote:
> > Mark Kettenis wrote:
> > > > From: "Ted Unangst"
> > > > Date: Mon, 10 Dec 2018 14:14:08 -0500
> > > > Content-Type: text/plain; charset=utf-8
> > > >
> > > >
On Tue, Dec 11, 2018 at 03:17:46PM -0200, Martin Pieuchot wrote:
> - Unify the two hooks by passing the same argument
> - Check for nullity before dereferencing `if_bridgeport', this will
> matter when we go MP
> - Use the same pattern to find a member in the ioctl path
>
> ok?
OK bluhm@
>
On Tue, Dec 11, 2018 at 02:40:16PM -0200, Martin Pieuchot wrote:
> ok?
OK bluhm@
> Index: kern/sysv_sem.c
> ===
> RCS file: /cvs/src/sys/kern/sysv_sem.c,v
> retrieving revision 1.53
> diff -u -p -r1.53 sysv_sem.c
> ---
On Tue, Dec 11, 2018 at 02:45:47PM -0200, Martin Pieuchot wrote:
> ok?
OK bluhm@
> Index: kern/sysv_shm.c
> ===
> RCS file: /cvs/src/sys/kern/sysv_shm.c,v
> retrieving revision 1.69
> diff -u -p -r1.69 sysv_shm.c
> ---
Mark Kettenis wrote:
> > From: "Ted Unangst"
> > Date: Mon, 10 Dec 2018 14:14:08 -0500
> > Content-Type: text/plain; charset=utf-8
> >
> > So I was actually looking at the passwd check rules because I wanted
> > to add a flag to disable the 3 bad passwords then ok whatever.
> >
> > This adds
On Tue, Dec 11, 2018 at 10:55:25PM +0100, Claudio Jeker wrote:
> On Tue, Dec 11, 2018 at 02:35:33PM -0700, Theo de Raadt wrote:
> > Ted Unangst wrote:
> >
> > > Marc Espie wrote:
> > > > > > - try to remove the files normally first
> > > > > > rm -f ${SUDO_CLEAN} || test -z "${SUDO}" ||
with the previous if_ethersubr.c diff, this allows etherip(4) to output
directly to the network stack.
direct output relies on the interface using priq, since hfsc uses the
ifq machinery to work. priq implies you dont want to delay packets, so
it lets etherip push the packet straight through.
i
Marc Espie wrote:
> There is a kind of mixed model there.
>
> Because make build still goes thru regress for obj and cleandir
>
> Yet the rest of the build doesn't!
>
> So, if we agree that it needs to stay the way it currently is, then
> the SUDO in that Makefile might trigger while running as
this makes it nicer to set up a custom output routine on ethernet
interfaces. rather than overwriting it after ether_ifattach is called,
you can set it up with the rest of the callbacks and the ether layer
will respect it.
ok?
Index: if_ethersubr.c
I have some trace files that are gzipped to save space. (They compress really
well.) It would be convenient if I could simply zcat them into kdump for
inspection.
This patch allows -f - to read from stdin. (Curiously, kdump always reads from
stdin, but uses freopen on the trace file.)
Unsure
ok deraadt
Index: dev/pci/pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1870
diff -u -p -r1.1870 pcidevs
--- dev/pci/pcidevs 30 Nov 2018 19:18:31 - 1.1870
+++ dev/pci/pcidevs 12 Dec 2018 04:47:11
On Wed, Dec 12, 2018 at 11:54:39AM +1000, David Gwynne wrote:
> this makes it nicer to set up a custom output routine on ethernet
> interfaces. rather than overwriting it after ether_ifattach is called,
> you can set it up with the rest of the callbacks and the ether layer
> will respect it.
>
>
So I got puzzled because of a behavioural difference between snmpwalk
and snmpctl walk.
snmp returns the next element after the requested element for a
getNextRequest. So for a leaf-element this can be it's closest
neighbour. e.g.
$ make && snmpctl snmp walk host oid 1.3.6.1.4.1.9.9.273.1.1.2.1.1
The diff below allows me to walk oids that contain a 0, while at the
same time disallow the walking of neighbouring nodes.
I only lightly tested this with snmpctl walk and I haven't looked at
how snmpd hooks into this, but considering reyk put the function there
with the "Add initial SNMP client
As requested by deraadt@, here's a diff that includes the leaf value
itself.
$ ./snmpctl snmp walk host oid 1.3.6.1.4.1.9.9.273.1.1.2.1.1
1.1=1
1.2=5
$ ./snmpctl snmp walk host oid 1.3.6.1.4.1.9.9.273.1.1.2.1.1.1
1=1
$
On 12/11/18 1:10 PM, Martijn van Duren wrote:
> So I got puzzled because of
On Mon, Dec 10, 2018 at 11:44:47AM +0100, Otto Moerbeek wrote:
> On Mon, Dec 10, 2018 at 08:30:10AM +0100, Otto Moerbeek wrote:
>
> > Hi,
> >
> > the bootloader uses a very simple allocator for dynamic memory. It
> > maintains a list of free allocations. If it needs a block, it searches
> > the
33 matches
Mail list logo
