Re: /usr/libexec/security symlink permission check warnings

2016-04-10 Thread Antoine Jacoutot
> Changing which mode is checked won't help you because security(8) > also complains that printcap(5) is a symlink rather than the expected > regular file. So you would still et spammed. > > Antoine, is it normal that CUPS replaces /etc/printcap with a symlink? Yes it is. > Any idea how to prev

Re: /usr/libexec/security symlink permission check warnings

2016-04-10 Thread Stuart Henderson
On 2016/04/10 18:50, Ingo Schwarze wrote: > [Cc:ing the print/cups maintainer] > > Hi Stephen, > > Stephen Hassard wrote on Sat, Apr 09, 2016 at 06:30:04PM +: > > > After installing the cups package I'm getting a warning from the daily > > insecurity check about /etc/printcap. > > > > The s

Re: /usr/libexec/security symlink permission check warnings

2016-04-10 Thread Ingo Schwarze
[Cc:ing the print/cups maintainer] Hi Stephen, Stephen Hassard wrote on Sat, Apr 09, 2016 at 06:30:04PM +: > After installing the cups package I'm getting a warning from the daily > insecurity check about /etc/printcap. > > The security output is as follows: > --- > Checking special files a

can't set lladdr on apu1 re(4) nics (vlan over trunk problem?) on 5.9

2016-04-10 Thread Daniel Jakots
Hi, I just upgraded to OpenBSD 5.9 -stable for my apu which I use as home router. My setup is 3 vlans over a trunk lacp between re0 and re2 while re1 goes to my ISP black box which gives it an IP through dhcp. When it boots, it says: starting network re0: PHY write failed re0: PHY write failed D