Re: tcpdump fork+exec?

2017-09-06 Thread Bryan Steele
On Thu, Sep 07, 2017 at 06:58:28AM +0200, Otto Moerbeek wrote: > On Thu, Sep 07, 2017 at 12:27:18AM -0400, Bryan Steele wrote: > > > Hi, > > > > This turned out easier then pflogd thanks to the existing privsep design > > work done by deraadt@ and canacar@ many years ago. While tcpdump isn't a >

Re: tcpdump fork+exec?

2017-09-06 Thread Theo de Raadt
> done by otto@ and cancacar@ while being prodded almost gently by deraadt@ So untrue. I don't do gently...

Re: tcpdump fork+exec?

2017-09-06 Thread Otto Moerbeek
On Thu, Sep 07, 2017 at 12:27:18AM -0400, Bryan Steele wrote: > Hi, > > This turned out easier then pflogd thanks to the existing privsep design > work done by deraadt@ and canacar@ many years ago. While tcpdump isn't a Small correction for the record: done by otto@ and cancacar@ while being pr

tcpdump fork+exec?

2017-09-06 Thread Bryan Steele
Hi, This turned out easier then pflogd thanks to the existing privsep design work done by deraadt@ and canacar@ many years ago. While tcpdump isn't a daemon in the traditional sense, it isn't so uncommon for people to have long running sessions. At least on OpenBSD, this is even safe thanks to pri

Re: SSE2 instructions emitted in libcompiler_rt

2017-09-06 Thread Mike Larkin
On Wed, Sep 06, 2017 at 11:54:38PM +0200, Patrick Wildt wrote: > On Wed, Sep 06, 2017 at 11:43:15PM +0200, Christian Weisgerber wrote: > > Somebody noticed this on FreeBSD: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221733 > > > > On i386, libcompiler_rt includes assembly implementation

Re: SSE2 instructions emitted in libcompiler_rt

2017-09-06 Thread Mike Larkin
On Wed, Sep 06, 2017 at 11:43:15PM +0200, Christian Weisgerber wrote: > Somebody noticed this on FreeBSD: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221733 > > On i386, libcompiler_rt includes assembly implementations for > floating point conversion functions that unconditionally use SSE2

Re: SSE2 instructions emitted in libcompiler_rt

2017-09-06 Thread Patrick Wildt
On Wed, Sep 06, 2017 at 11:43:15PM +0200, Christian Weisgerber wrote: > Somebody noticed this on FreeBSD: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221733 > > On i386, libcompiler_rt includes assembly implementations for > floating point conversion functions that unconditionally use SSE2

SSE2 instructions emitted in libcompiler_rt

2017-09-06 Thread Christian Weisgerber
Somebody noticed this on FreeBSD: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221733 On i386, libcompiler_rt includes assembly implementations for floating point conversion functions that unconditionally use SSE2 instructions, which are not supported by older CPUs. Specifically, these files

Re: [PATCH v2 2/2] VMD: Prevent vmd crashing when stopping a stopped vm

2017-09-06 Thread Carlos Cardenas
On 2017-09-05 23:55, Mike Larkin wrote: > On Mon, Sep 04, 2017 at 12:03:31AM -0700, Carlos Cardenas wrote: >> * Fix logic handling stopping a VM. Prevents VMD from crashing. >> * Add additional error code to notify the user that a vm cannot be >> stopped when not running. >> * Add additional log

If devs need any old Dell spares

2017-09-06 Thread Tom Smyth
Hello if devs need some spares for older dell systems / hp systems let me know and Ill see if I have the parts. DRAC Cards, PERC Controlers Power Supplies Let me know and Ill ship them to you Thanks Tom Smyth

Re: want some working PCI-e 4Port Nics Atheros Chipset

2017-09-06 Thread Tom Smyth
sorry forgot to mention these are copper RJ45 cards (not sfp) Thanks On 6 September 2017 at 19:29, Tom Smyth wrote: > > Hello lads & Ladies > > I have a few Port Gb/s PCI-E (X4) Cards > from a few systems Im retiring > > Product name Mikrotik RB44Ge > Chipset Atheros AR8131/M > PCIe 4X >

Need Hotswap Seagate 300GB 10K U320 SCSI Drives ?

2017-09-06 Thread Tom Smyth
Hello Lads & Ladies 8x working Ultra U320 10K 300G Seagate Cheetah ST337LC I have a few 15K 73GB Ultra 320 Drives also not super awesome but may help for spares for aging systems that you want to test on Im willing to ship them to Developers / porters if they think they would help them

want some working PCI-e 4Port Nics Atheros Chipset

2017-09-06 Thread Tom Smyth
Hello lads & Ladies I have a few Port Gb/s PCI-E (X4) Cards from a few systems Im retiring Product name Mikrotik RB44Ge Chipset Atheros AR8131/M PCIe 4X Formfactor Full / Half Height half Lenghth i have fullheight brackets on them and Ill try to root out the half height brackets if I ca

Re: softraid: force assemble issues

2017-09-06 Thread Patrick Wildt
On Wed, Sep 06, 2017 at 07:10:15PM +0200, Patrick Wildt wrote: > On Wed, Sep 06, 2017 at 05:44:21PM +0200, Patrick Wildt wrote: > > Hi, > > > > I'm testing some SoftRAID in a Mirroring setup and stumbled upon > > something. When I set a disk offline, zero out the disk and the > > metadata blocks,

Re: softraid: force assemble issues

2017-09-06 Thread Patrick Wildt
On Wed, Sep 06, 2017 at 05:44:21PM +0200, Patrick Wildt wrote: > Hi, > > I'm testing some SoftRAID in a Mirroring setup and stumbled upon > something. When I set a disk offline, zero out the disk and the > metadata blocks, reboot, and then try to assemble it, it will > fail. Rightfully so, since

Re: lock(1): wipe hash before exit in one-time password case

2017-09-06 Thread Theo Buehler
On Wed, Aug 30, 2017 at 08:49:20PM -0500, Scott Cheloha wrote: > Hi, > > In the one-time password case we want to wipe the hash itself > before exit, right? Yes, clearing s1 there makes no sense anymore, it was already zeroed out further up. ok tb > > This must have slipped through when tedu@

Re: mg: extract exit status from pclose return value

2017-09-06 Thread Scott Cheloha
~2 week bump. Any thoughts or feedback? -- Scott Cheloha > On Aug 25, 2017, at 11:27 PM, Scott Cheloha wrote: > > Hi, > > compile_mode() currently just reports the value returned by > pclose(3). This is incorrect because pclose gives you > whatever wait4(2) returned, which needs to be examin

Re: [patch] ocspcheck: nextUpdate is optional according to RFC 6960

2017-09-06 Thread Andreas Bartelt
On 09/06/17 16:24, Bob Beck wrote: effectivelyu providing a limitless OCSP staple is kind of stupid - you may as well simply *not staple* I guess a stapled response without the next_update field set would be treated as valid until the client considers this_update to be too old (for ocspcheck

softraid: force assemble issues

2017-09-06 Thread Patrick Wildt
Hi, I'm testing some SoftRAID in a Mirroring setup and stumbled upon something. When I set a disk offline, zero out the disk and the metadata blocks, reboot, and then try to assemble it, it will fail. Rightfully so, since the metadata information is completely gone from one disk. That's not a r

Re: warnings in pax

2017-09-06 Thread Alexander Bluhm
On Wed, Sep 06, 2017 at 04:25:55PM +0200, Otto Moerbeek wrote: > clang complains about a quite some signed compares in pax. This fixes > a few of them, all of the form > > if (var < sizeof(...)) > > where var is an int. > > Here a conversion of the int value to unsigned takes place, due to

fix -Wuninitialized in kernel

2017-09-06 Thread Alexander Bluhm
Hi, I have compiled the kernel with clang -Wuninitialized and would like to fix these findings: - toshiba_hotkey() is a bug - in rasops_bitops.h is useless code - in elf_load_file() it is nicer to call free(NULL, type, 0) instead of free(NULL, type, undefined). Not a real bug as free(9) checks

warnings in pax

2017-09-06 Thread Otto Moerbeek
Hi, clang complains about a quite some signed compares in pax. This fixes a few of them, all of the form if (var < sizeof(...)) where var is an int. Here a conversion of the int value to unsigned takes place, due to the conversion rules. This causes negative values of var not to be caug

Re: [patch] ocspcheck: nextUpdate is optional according to RFC 6960

2017-09-06 Thread Bob Beck
effectivelyu providing a limitless OCSP staple is kind of stupid - you may as well simply *not staple* On Wed, Sep 6, 2017 at 8:23 AM, Bob Beck wrote: > I'm not super inclined to make this "flexible" unless we see this used int > the wild, which I have not. We are more restrictive than > OpenSSL

Re: [patch] ocspcheck: nextUpdate is optional according to RFC 6960

2017-09-06 Thread Bob Beck
I'm not super inclined to make this "flexible" unless we see this used int the wild, which I have not. We are more restrictive than OpenSSL in many areas. On Wed, Sep 6, 2017 at 1:31 AM, Andreas Bartelt wrote: > On 09/06/17 04:40, Bob Beck wrote: > >> Andreas where are you seeing this as being a

Re: cwm: Don't ignore case when sorting exec menu

2017-09-06 Thread Okan Demirmen
On Sun, Sep 3, 2017 at 3:43 PM, wrote: > Hi tech@ > ​, > ​Hi, ​ > ​ > > I wasn't able to execute "zzz" (lower case) from the exec menu in cwm. > It > skipped over it when ordering the search results because "ZZZ" (upper > case) was already there > ​. > ​Indeed, I agree that case matters here.

Re: [patch] ocspcheck: nextUpdate is optional according to RFC 6960

2017-09-06 Thread Andreas Bartelt
On 09/06/17 04:40, Bob Beck wrote: Andreas where are you seeing this as being a real issue - who is shipping out OCSP responses without a next update field? I've noticed this while playing with a local CA and a corresponding OCSP responder on my LAN. For openssl ocsp, the -nmin or -ndays argu

Re: [patch] ocspcheck: nextUpdate is optional according to RFC 6960

2017-09-06 Thread Andreas Bartelt
On 09/06/17 04:40, Bob Beck wrote: Andreas where are you seeing this as being a real issue - who is shipping out OCSP responses without a next update field? I've noticed this while playing with a local CA and a corresponding OCSP responder on my LAN. For openssl ocsp, the -nmin or -ndays argu