proposal: syspatch -v

At present, what exactly was patched is not immediately obvious from syspatch output, which could be annoying for administrators who want to take some action based on what was changed (restart daemons linked to patched libraries, etc). Could a -v option for syspatch (patch below), causing it to

[patch] security(8) and spamd blacklist

Hi, security(8) iterates over /var/mail and check is the files belong to the owner of the same name. So far so good, but spamd.conf.5 says: override:\ :white:\ :method=file:\ :file=/var/mail/override.txt: myblack:\ :black:\

magic.5: Add missing types

While reading file(1)'s code in #openbsd-daily mulander noted that the 'name' and 'use' types were missing from magic(5). I'm not entirely sure yet whether this is complete, so here's what I did: magic(5) provided by devel/magic documents version 5.31 while base's magic(5) is at 4.24. Here are

Re: proposal: syspatch -v

> Peter Piwowarski wrote: > > At present, what exactly was patched is not immediately obvious from > > syspatch output, which could be annoying for administrators who want to > > take some action based on what was changed (restart daemons linked to > > patched libraries, etc). Could a -v option

Re: ktrace: Following symlinks

On Thu, Jun 29, 2017 at 09:50:25PM -0700, Philip Guenther wrote: On Thu, Jun 22, 2017 at 7:17 PM, Klemens Nanni wrote: So I just wrapped my head around vfs(9) with regard to making ktrace following symlinks again, however I don't quite understand what problems may occur when

Re: proposal: syspatch -v

Peter Piwowarski wrote: > At present, what exactly was patched is not immediately obvious from > syspatch output, which could be annoying for administrators who want to > take some action based on what was changed (restart daemons linked to > patched libraries, etc). Could a -v option for syspatch

Re: ktrace: Following symlinks

On Thu, Jun 22, 2017 at 7:17 PM, Klemens Nanni wrote: > So I just wrapped my head around vfs(9) with regard to making ktrace > following symlinks again, however I don't quite understand what problems > may occur when doing so. May anyone enlighten me on this? IMHO, it makes more

Re: [patch] security(8) and spamd blacklist

On 2017/06/29 21:37, Fritjof Bornebusch wrote: > Hi, > > security(8) iterates over /var/mail and check is the files belong to the > owner of the same name. So far so good, but spamd.conf.5 says: > > override:\ > :white:\ > :method=file:\ > :file=/var/mail/override.txt:

fix relayd dns protocol

Hi! config_setrelay>relay_privinit>relay_udp_privinit doesn't set env since env isn't set in relay.c yet, causing dns relay to SIGSEGV in relay_udp_server. Move setting env to relay_udp_init. Rivo Index: usr.sbin/relayd/relay.c ===

Re: [patch] security(8) and spamd blacklist

On Thu, Jun 29, 2017 at 10:06:56PM +0100, Stuart Henderson wrote: > On 2017/06/29 21:37, Fritjof Bornebusch wrote: > > Hi, > > > > security(8) iterates over /var/mail and check is the files belong to the > > owner of the same name. So far so good, but spamd.conf.5 says: > > > > override:\ > >

csh(1): remove size parameter from tenex()

Hi, Both the old (prior getting rid of TIOCSTI) and the new implementation of tenex() makes assumptions about the capacity of the input buffer without respect to the inputline_size parameter. A more correct handling would be to set `cl.size = MIN(BUFSIZ, inputline_size)` but since tenex() only has

ip6_forward pf rtable change

Hi, In OpenBSD 6.0 we had the check (ip6_forward_rt.ro_tableid != m->m_pkthdr.ph_rtableid) after going to reroute in ip6_forward(). As this was lost during refactoring, now the old route is used after pf has changed the routing table. Solution is to reset the route, then it is not valid and will

Re: no-depends for real, the juicy part

On Wed, Jun 28, 2017 at 04:59:37PM +0200, Marc Espie wrote: > This is the actual patch that more or less neuters depends. > > So this gets rid of all internals for depend/beforedepend/afterdepend. > > NOTE that this does not *remove* the 'make depend' stage, just it won't do > anything except

Re: tty(4): mention TIOCSTAT

On Wed, Jun 28, 2017 at 03:41:29PM -0600, Todd C. Miller wrote: > On Wed, 28 Jun 2017 15:35:36 -0600, "Theo de Raadt" wrote: > > > Nope. It requires a parameter. lukem messed this up two decades ago, > > he should have used _IO but used the wrong one. > > Ah right, I missed that it is _IOW.

vi(1): remove stub settings

Hi, >From vi(1): lisp [off] (...) This option is not yet implemented. modelines, modeline [off] (...) This option will never be implemented. optimize, opt [on] (...) This option is not yet implemented redraw, re [off]

mfi(4): Make "bioctl -R" work after hot swapping

Hi tech@, Currently "bioctl -R" works only if disk state is "Offline" (set by "bioctl -O") and it doesn't work for "Failed" disk. To make it work with hot swapped disk, report unused ("unconfigured" in MegaRAID) disk to userland, and handle it properly when rebuilding. Notes about

Re: unbound 1.6.4

On 2017/06/27 14:58, Stuart Henderson wrote: > If anyone's interested in newer unbound, I have an initial diff, it's > 750K all-in (we are currently on 1.6.1 so there are a few releases worth > of changes) so I won't send it inline, it's at > https://junkpile.org/unbound-1.6.4.diff > I had a

Re: dig(1) doesn't play well with rebound(8)

On Fri, May 26, 2017 at 08:08:08AM -0400, Ted Unangst wrote: > Edgar Pettijohn wrote: > > This may not be the best way to handle this, but it was the first fix to > > come to mind. Not sure where to put this in the manual or if its even > > worth documenting. Thoughts? > > I think this is a

Re: dig(1) doesn't play well with rebound(8)

I played with it but kept getting segfaults. So moved my version with a command line option to /use/local. I guess Im the only person using rebound and dig. ⁣Sent from BlueMail ​ On Jun 29, 2017, 4:13 AM, at 4:13 AM, Theo Buehler wrote: >On Fri, May 26, 2017 at 08:08:08AM

Re: dig(1) doesn't play well with rebound(8)

nslookup also seems to get a little upset with rebound. On 29 June 2017 at 13:13, Edgar Pettijohn wrote: > I played with it but kept getting segfaults. So moved my version with a > command line option to /use/local. I guess Im the only person using rebound > and dig. >