On Fri, Oct 07, 2016 at 03:06:28PM -0500, Brent Cook wrote:
>
> > On Oct 7, 2016, at 2:52 PM, Otto Moerbeek wrote:
> >
> > On Fri, Oct 07, 2016 at 02:33:13PM -0500, Brent Cook wrote:
> >
> >>
> >>> On Oct 7, 2016, at 12:18 PM, Ted Unangst wrote:
> >>>
> >>> Kinichiro Inoguchi wrote:
>
Hello -
Many operating systems out there are starting to enable TCP ECN by
default, most inbound-only. Linux, FreeBSD, Apple MacOS and iOS.
This diff mimicks the FreeBSD diff found at
http://marc.info/?l=freebsd-commits-all&m=146369644516347&w=2
It modifies the net.inet.tcp.ecn from an off and
Sorry for my misunderstanding, and thanks for teaching me.
I had read C99 standard document.
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf
On p.130 6.7.8 Initialization "32 EXAMPLE 8 The declaration" says,
-
char s[] = "abc", t[3] = "abc";
defines ‘‘plain’’ char array obj
I want to make route_output and route_input and a few other things in
rtsock.c less hostile so here is a refactoring of the code.
Main goal is to make it clearer how the return packet is generated.
--
:wq Claudio
Index: net/rtsock.c
===
Same same but one line of code less and no more goto.
OK?
--
:wq Claudio
Index: net/raw_usrreq.c
===
RCS file: /cvs/src/sys/net/raw_usrreq.c,v
retrieving revision 1.24
diff -u -p -r1.24 raw_usrreq.c
--- net/raw_usrreq.c5 Sep 201
This is now working on www.openbsd.org. I upgraded my
6.0 system to current today off the latest snap and httpd would
not start, same problem.
This diff lets current httpd start again.
ok beck@
On Tue, Oct 04, 2016 at 11:54:37PM +0200, Rafael Zalamena wrote:
> On Tue, Oct 04, 2016 at 07:46
ks_tables.h is always considered out of date due to the forced rebuild
of the makekeys util. This means it's also rebuilt during install. First
as root during build, later by the BUILDUSER during release, which won't
be able to rewrite it, because it's now owned by root. With this result:
Brent Cook wrote:
>
> > On Oct 7, 2016, at 12:18 PM, Ted Unangst wrote:
> >
> > Kinichiro Inoguchi wrote:
> >> I think this 16 bytes string assignment has boundary issue.
> >>
> >>static const char sigma[16] = "expand 32-byte k";
> >>
> >> I found this when I tried to build libressl-portab
> On Oct 7, 2016, at 2:52 PM, Otto Moerbeek wrote:
>
> On Fri, Oct 07, 2016 at 02:33:13PM -0500, Brent Cook wrote:
>
>>
>>> On Oct 7, 2016, at 12:18 PM, Ted Unangst wrote:
>>>
>>> Kinichiro Inoguchi wrote:
I think this 16 bytes string assignment has boundary issue.
static c
On Fri, Oct 07, 2016 at 02:33:13PM -0500, Brent Cook wrote:
>
> > On Oct 7, 2016, at 12:18 PM, Ted Unangst wrote:
> >
> > Kinichiro Inoguchi wrote:
> >> I think this 16 bytes string assignment has boundary issue.
> >>
> >>static const char sigma[16] = "expand 32-byte k";
> >>
> >> I found
> On Oct 7, 2016, at 12:18 PM, Ted Unangst wrote:
>
> Kinichiro Inoguchi wrote:
>> I think this 16 bytes string assignment has boundary issue.
>>
>>static const char sigma[16] = "expand 32-byte k";
>>
>> I found this when I tried to build libressl-portable with MSVC on Windows.
>
> anothe
Generate the pkg-config files at build time, otherwise we might run into
permission issues with noperm release builds. While there properly clean
up glw.pc. Ok?
natano
Index: lib/libGLw/Makefile
===
RCS file: /cvs/xenocara/lib/libGL
On Fri, 07 Oct 2016 12:39:18 +0200, Jan Stary wrote:
> The sort(1) manpage mentions the LC_* environment variables
> and how they affect sorting and efficiency, but we only
> support LC_CTYPE, right? Would it be an omprovement
> to remove these from the manpage?
The code supports collation based
Kinichiro Inoguchi wrote:
> I think this 16 bytes string assignment has boundary issue.
>
> static const char sigma[16] = "expand 32-byte k";
>
> I found this when I tried to build libressl-portable with MSVC on Windows.
another broken compiler? the above line is perfectly valid C.
On Fri, Oct 07, 2016 at 03:28:19PM +0200, Stefan Sperling wrote:
> Currently tcpdump shows "0 Mbit/s" for any frame sent with 11n HT MCS.
> To make progress easier, I'd like to see which MCS are used on the air,
> by any device.
>
> The change below matches what FreeBSD did to pass an MCS index vi
Hi,
I think this 16 bytes string assignment has boundary issue.
static const char sigma[16] = "expand 32-byte k";
I found this when I tried to build libressl-portable with MSVC on Windows.
These 4 files have the same code above.
lib/libc/crypt/chacha_private.h
lib/libcrypto/chacha/chacha-
> Date: Fri, 7 Oct 2016 16:32:35 +0200
> From: Frederic Cambus
>
> Hi tech@,
>
> It seems there are still some leftovers from the zaurus port removal.
>
> Comments? OK?
Not ok. This is support for the zaurus as a usb device attached to an
OpenBSD machine. Perhaps the option should be renamed
Hi tech@,
It seems there are still some leftovers from the zaurus port removal.
Comments? OK?
Index: sys/dev/usb/if_cdce.c
===
RCS file: /cvs/src/sys/dev/usb/if_cdce.c,v
retrieving revision 1.71
diff -u -p -r1.71 if_cdce.c
--- sys/d
Jeremie Courreges-Anglas writes:
> Jeremie Courreges-Anglas writes:
>
>> j...@wxcvbn.org (Jeremie Courreges-Anglas) writes:
>>
>>> SNMP uses UDP and snmpd listens on a single address. This means that
>>> you can have issues with the source address of the replies sent by
>>> snmpd. "listen on $
Currently tcpdump shows "0 Mbit/s" for any frame sent with 11n HT MCS.
To make progress easier, I'd like to see which MCS are used on the air,
by any device.
The change below matches what FreeBSD did to pass an MCS index via radiotap.
This simply writes the MCS index into a previously unused range
Imre Vadasz pointed out that rate sets managed by net80211 are sorted
by effective data rate speed, while the iwm_rates array sorts CCK rates
(1 - 11 Mbit/s) before OFDM rates (6Mbit/s - 54Mbit/s).
rate set (11g): 1, 2, 5.5, 6, 9, 11, 12, 18, 24, 36, 54
iwm_rates: 1, 2, 5.5, 11, 6, 9, 12, 18,
On Thu, Oct 06, 2016 at 12:13:20PM +0200, Mike Belopuhov wrote:
> On Thu, Oct 06, 2016 at 10:11 +0900, YASUOKA Masahiko wrote:
> >
> > On Wed, 5 Oct 2016 14:30:27 +0200
> > Mike Belopuhov wrote:
> > > On Wed, Oct 05, 2016 at 10:58 +0900, YASUOKA Masahiko wrote:
> > >> On Tue, 4 Oct 2016 17:27:12
The sort(1) manpage mentions the LC_* environment variables
and how they affect sorting and efficiency, but we only
support LC_CTYPE, right? Would it be an omprovement
to remove these from the manpage?
Jan
Index: sort.1
===
23 matches
Mail list logo