Re: 7.3: Squid 6.3 with multiple workers - net.unix.dgram.sendspace too low

2023-10-21 Thread Silamael Darkomen
On 20 Oct 2023 19:33, Stuart Henderson wrote: After a few hours digging around, I eventually figured out where the relevant sockets are created and have added a patch (to 7.4-stable and -current) to bump buffers on them. Hi Stuart, Meanwhile I also did some digging and opened a bug at Squid wi

Re: 7.3: Squid 6.3 with multiple workers not starting - net.unix.dgram.sendspace too low

2023-10-19 Thread Silamael Darkomen
On 19 Oct 2023 16:36, Silamael Darkomen wrote: Hi, I just upgraded to Squid 6.3 under 7.3 and noticed that it no longer starts if configured to use multiple worker processes. After some debugging I found that net.unix.dgram.sendspace with its 2k limit is the reason. Squid uses Unix sockets

7.3: Squid 6.3 with multiple workers - net.unix.dgram.sendspace too low

2023-10-19 Thread Silamael Darkomen
Hi, Today I upgraded to the brand new Squid version 6.3 from ports and noticed, that Squid no longer starts properly if configured with multiple worker processes. After some debugging the limit from net.unix.dgram.sendspace came up as cause. The 2k default is way to low. In ktrace I saw sen

7.3: Squid 6.3 with multiple workers not starting - net.unix.dgram.sendspace too low

2023-10-19 Thread Silamael Darkomen
Hi, I just upgraded to Squid 6.3 under 7.3 and noticed that it no longer starts if configured to use multiple worker processes. After some debugging I found that net.unix.dgram.sendspace with its 2k limit is the reason. Squid uses Unix sockets for IPC and sends messages larger than those 2k

CVE-2018-12015: Directory Traversal in Archive::Tar

2018-06-13 Thread Silamael
Hi, The version of Archive::Tar part of the base system's Perl contains CVE-2018-12015: Original bug report: https://rt.cpan.org/Public/Bug/Display.html?id=125523 Original commit with the fix: https://github.com/jib/archive-tar-new/commit/ae65651eab053fc6dc4590dbb863a268215c1fc5 The vul

CVE-2018-12015: Directory Traversal in Archive::Tar

2018-06-12 Thread Silamael
Hi, The version of Archive::Tar part of the base system's Perl contains CVE-2018-12015: Original bug report: https://rt.cpan.org/Public/Bug/Display.html?id=125523 Original commit with the fix: https://github.com/jib/archive-tar-new/commit/ae65651eab053fc6dc4590dbb863a268215c1fc5 The vulne

Re: [PATCH] sensorsd - Command line switch for alternative configuration file

2017-03-15 Thread Silamael
On 14.03.2017 12:55, Alexander Bluhm wrote: > All other error messages are lower case. I would write "err(1, > "access configuration file %s", configfile)" as err(3) privides a > reason anyway. > > apart from that OK bluhm@ > Upated diff. -- Matthias Index: sensorsd.8

[PATCH] sensorsd - Command line switch for alternative configuration file

2017-03-14 Thread Silamael
Hi there, I wrote some patch allowing to specify the path of the configuration file of sensorsd like it's done for other daemons. Greetings, Matthias Index: sensorsd.8 === RCS file: /usr/src/usr.sbin/sensorsd/sensorsd.8,v retrieving

amd64/identcpu.c: Missing #ifdef CRYPTO for amd64_has_aesni

2013-04-08 Thread Silamael
Hi there, I think the check whether the CPU has AES builtin misses an #ifdef CRYPTO as it is there for the declaration of amd64_has_aesni. -- Matthias Index: identcpu.c === RCS file: /cvs/src/sys/arch/amd64/amd64/identcpu.c,v retri

Re: Remove explicit if_down() for removed trunk ports

2013-03-11 Thread Silamael
On 03/06/2013 04:37 PM, Stuart Henderson wrote: > I looked at this some time ago (because it's super annoying if you do > this on a remote system to swap the active port around and forget about > the behaviour ;) but I have some recollection there might have been > a bit more to it than this.. anyo

Remove explicit if_down() for removed trunk ports

2013-03-06 Thread Silamael
Hi, In if_trunk.c there's an explicit if_down() for trunk ports being removed from the trunk. This seems unnecessary to me and is there since the trunk feature has initially added to OpenBSD. Greetings, Matthias === diff --git a/sy

pfctl -n should not call getifmtu for altq

2012-04-26 Thread Silamael
Hello, We distributed the pf.conf for several machines from a central server. If we configure altq using interface names not existing on this server, it is not possible to run pfctl -nf without an error from the SIOCGIFMTU ioctl call in getifmtu(). This patch prevents the call to getifmtu() if pfc