RFC 5071 DHCP options

I use dhcpd(8) to boot some boxes with PXELINUX. The numbered options work but dhcpd.conf(5) is easier to maintain with names. These options are defined in RFC 5071. Nathanael Index: sbin/dhclient/tables.c === RCS file: /cvs/src/sbin

Should PIE be mentioned in security.html?

Not sure about its location in the list. Index: security.html === RCS file: /cvs/www/security.html,v retrieving revision 1.422 diff -u -p -r1.422 security.html --- security.html 2 Jul 2015 05:49:04 - 1.422 +++ security

synaptics touchpads: w mode and resolution

Some weeks ago a change was made in pms to support Synaptics touchpads that don't provide W mode. I assume that only fairly old models are concerned, and that the variant in the patch below is more accurate. It only fakes W values where necessary. The patch contains a second change, a check whet

Re: squid 3.5/trunk and SSLv3 removal

On Friday 28 August 2015 13:19:17 Stuart Henderson wrote: > Any suggestions as to what might be needed here, can the SSLv3_method > just be replaced with SSLv23_method? Yes, that should be fine. The code is parsing an SSLv3/TLS client hello message and it is then mapping the ciphersuites to libss

Re: syslogd host matches ip

On Fri, Aug 28, 2015 at 06:11:02PM +0200, Alexander Bluhm wrote: > The +host feature allows to select log messages from a specific > host. Normally syslogd does a reverse lookup on the sender's > address. If that fails or if syslogd has been started with the -n > option, the +host is matched with

LibreSSL 2.2.3 Prerelease available for testing

We have put together a prerelease of LibreSSL 2.2.3. This release primarily targets a bug that causes connections with some SSL clients to fail during the initial handshake. Preliminary release notes and a tarball are available at the following link: https://github.com/libressl-portable/portable/r

syslogd host matches ip

Hi, The +host feature allows to select log messages from a specific host. Normally syslogd does a reverse lookup on the sender's address. If that fails or if syslogd has been started with the -n option, the +host is matched with the IP. Unfortunatelty IP addresses consist of characters that are

Re: readelf on mips64

On Fri, Aug 28, 2015 at 12:00:41PM +0200, Mark Kettenis wrote: > As Theo and I noticed yesterday: > > $ readelf -a /usr/lib/libc.a > readelf: Error: /usr/lib/libc.a: invalid archive string table offset 0 > > Turns out that on mips64 binutils creates IRIX-style "64-bit" archives > which allege

Re: diff - more satosin/sintosa

3rd update. Thanks to Kent for testing. === RCS file: /cvs/src/sys/net/if_gif.c,v retrieving revision 1.77 diff -u -p -r1.77 if_gif.c --- sys/net/if_gif.c17 Jul 2015 18:05:59 - 1.77 +++ sys/net/if_gif.c28 Aug 2015 1

squid 3.5/trunk and SSLv3 removal

Any suggestions as to what might be needed here, can the SSLv3_method just be replaced with SSLv23_method? http://bazaar.launchpad.net/~squid/squid/3.5/view/head:/src/ssl/bio.cc#L1009 | ciphers += 2; | if (ciphersLen) { | const SSL_METHOD *method = SSLv3_method();

Introducing rtvalid(9)

Multiples routing entry issues, including my recent rtalloc(9) rewrite, led me to believe that we need a simple way to check if a (cached) route is still valid. So let me introduce rtvalid(9): The rtvalid() function checks if the route entry rt is still valid and can be used. Cached en

readelf on mips64

As Theo and I noticed yesterday: $ readelf -a /usr/lib/libc.a readelf: Error: /usr/lib/libc.a: invalid archive string table offset 0 Turns out that on mips64 binutils creates IRIX-style "64-bit" archives which allegedly can be larger than 4GB. The difference is apparently in the archive map

Re: Using tame() in userland

have a much more stringent one for tsort. Index: tsort.c === RCS file: /build/data/openbsd/cvs/src/usr.bin/tsort/tsort.c,v retrieving revision 1.26 diff -u -p -r1.26 tsort.c --- tsort.c 29 Jul 2015 10:42:37 - 1.26 +++

Re: [patch] fix sdmmc bug affecting strictly sector-addressable eMMC chips

> Nice work! I wonder why you chose to be so conservative (or arbitrary) > about the "after 50 failed attempts" condition. :) My reasoning is that after 50 failed CMD1s, either two things are the case: The card will only initialize with the sector bit set, or it is a high capacity device taking a

Re: [patch] fix sdmmc bug affecting strictly sector-addressable eMMC chips

On Fri, Aug 28, 2015 at 02:13:44AM -0400, kremlin wrote: > sdmmc gives up configuring the card after 100 failed CMD1 commands. My > patch starts asserting the MMC_OCR_SECTOR_MODE bit after 50 failed > attempts. This fixes the bug on my BBB with Micron chip: Nice work! I wonder why you chose to be