Re: Why are you so mean dhclient ?

On Fri, Feb 5, 2016 at 3:44 PM, sven falempin wrote: > > > On Fri, Feb 5, 2016 at 3:40 PM, sven falempin > wrote: > >> Dear Allmighty Tech Readers, >> >> I recently found out that you cannot dhclient a carp iface. >> People jumped over that saying , blahblah must have ip . >> Lies ! CARP require

Why are you so mean dhclient ?

Dear Allmighty Tech Readers, I recently found out that you cannot dhclient a carp iface. People jumped over that saying , blahblah must have ip . Lies ! CARP require the two interface to have the same ip, the mac will be the same so using dhcp to configure them is working by design. I have now a

Re: Why are you so mean dhclient ?

On Fri, Feb 5, 2016 at 3:40 PM, sven falempin wrote: > Dear Allmighty Tech Readers, > > I recently found out that you cannot dhclient a carp iface. > People jumped over that saying , blahblah must have ip . > Lies ! CARP require the two interface to have the same ip, > the mac will be the same so

Re: [patch] kern/exec_script: return error when the shell name is not specified

Michael McConville wrote: > Michael McConville wrote: > > Maxim Pugachev wrote: > > > In a case when the shell name is not specified (i.e. just "#!" without > > > a path), don't run the heavy logic that checks shell, simply return > > > ENOENT. > > > > I'm not sure whether this is a reasonable thi

Re: fix iwn ccmp replay detection

On Fri, Feb 05, 2016 at 03:41:17PM +0100, Stefan Sperling wrote: > Also, align the sequence number replay check with what ieee80211_input() does. On second thought, I'm retracting my change to the sequence number check. This check is about replay detection to make attacks on the crypto harder, not

Re: multicast, ETOOMANYREFS and intro(2)

On 05/02/16(Fri) 14:06, Jérémie Courrèges-Anglas wrote: > Martin Pieuchot writes: > > > On 01/02/16(Mon) 13:15, Todd C. Miller wrote: > >> On Mon, 01 Feb 2016 19:56:01 +0100, > >> =?utf-8?Q?J=C3=A9r=C3=A9mie_Courr=C3=A8ges- > >> Anglas?= wrote: > >> > >> > intro(2) describes it as such: > >> >

Re: mbtowc(3) errno for incomplete character

Hi Stefan, Stefan Sperling wrote on Fri, Feb 05, 2016 at 04:06:50PM +0100: > On Fri, Feb 05, 2016 at 03:53:44PM +0100, Ingo Schwarze wrote: >> Index: mbtowc.c >> === >> RCS file: /cvs/src/lib/libc/locale/mbtowc.c,v >> retrieving revi

Re: Some df(1) cleanup

Hi, Theo Buehler wrote on Mon, Feb 01, 2016 at 06:23:33PM +0100: > On Mon, Feb 01, 2016 at 05:41:25PM +0100, Theo Buehler wrote: >> On Mon, Feb 01, 2016 at 05:17:03PM +0100, Michal Mazurek wrote: >>> mntbuf = calloc(argc, sizeof(struct statfs)); >>> if (mntbuf == NULL) >>>

Re: mbtowc(3) errno for incomplete character

On Fri, Feb 05, 2016 at 03:53:44PM +0100, Ingo Schwarze wrote: > Index: mbtowc.c > === > RCS file: /cvs/src/lib/libc/locale/mbtowc.c,v > retrieving revision 1.2 > diff -u -p -r1.2 mbtowc.c > --- mbtowc.c 5 Dec 2012 23:20:00 -

mbtowc(3) errno for incomplete character

Hi, here is a very wide-spread bug, affecting all operating systems i was able to check. What happens if an incomplete character is passed to mbtowc(3)? POSIX is quite clear: If s is not a null pointer, mbtowc() shall either return 0 (if s points to the null byte), or return the number of b

fix iwn ccmp replay detection

iwn currently flags A-MPDU subframes which arrived out of sequence as CCMP replays and drops them. We can't rely on the LAST_RX_AMPDU flag from the last RX PHY notification, it seems. Check for a valid BA agreement instead. Updating the last seen packet number with every out-of-order packet isn't

Re: rtadvd usage()

On Fri, Feb 05, 2016 at 01:26:02PM +0100, J??r??mie Courr??ges-Anglas wrote: > The diff below adds __dead to relevant function decls and tidies up > log.h a bit. > > ok? OK bluhm@ > > Index: log.h > === > RCS file: /cvs/src/usr.sbi

Re: multicast, ETOOMANYREFS and intro(2)

Martin Pieuchot writes: > On 01/02/16(Mon) 13:15, Todd C. Miller wrote: >> On Mon, 01 Feb 2016 19:56:01 +0100, >> =?utf-8?Q?J=C3=A9r=C3=A9mie_Courr=C3=A8ges- >> Anglas?= wrote: >> >> > intro(2) describes it as such: >> > >> > 59 ETOOMANYREFS Too many references: can't splice. Not used in Ope

rtadvd unicast

rtadvd contains code to send unicast replies, RFC4861 mentions this possibility (section 6.2.6) but I'm having a hard time thinking how it could be useful. Since the sending part is commented out since it was introduced, I doubt that anyone will miss it. This removes pointless memory allocations

Re: rtadvd usage()

Alexander Bluhm writes: > On Thu, Feb 04, 2016 at 02:02:46PM +0100, J??r??mie Courr??ges-Anglas wrote: >> +static void usage(void); > > Can you make the usage static __dead void? gsoares made the same comment, there are other functions that could be marked __dead and I initially wanted to do the