Re: getentropy(2) and arc4random(3) do not reseed on VM fork

2024-08-25 Thread Bryan Stenson
Per Theo's comment here, maybe this really doesn't matter : https://marc.info/?l=openbsd-tech&m=172426918805083&w=2 Are you actually seeing identical values from arc4random(3) from VMs launched from the same snapshot? On Saturday, August 24, 2024, Bryan Stenson wrote: > I've not tested this, bu

Re: panic - mutex? - AMD64/7.4 to current

2024-08-25 Thread Martin Pieuchot
On 24/08/24(Sat) 13:14, Hugh Graham wrote: > On Sat, Aug 24, 2024 at 09:31:43PM +0200, Martin Pieuchot wrote: > > On 24/08/24(Sat) 12:09, Hugh Graham wrote: > > > The machine that slowly received the ports tree crashed upon reboot, > > > and I have included the traces. It was running 7.5-stable at

Re: pf af-to silently dropping packets that are too big after translation

2024-08-25 Thread Alexandr Nedvedicky
Hello, I did check things with tpcdump. And it looks like pf(4) is doing the right thing. let me explain. To play with pf(4) I'm using same network set up as we use for regression testing [1] [1] https://github.com/openbsd/src/blob/master/regress/sys/net/pf_forward/Makefile > >How-To-Repeat:

[ksh?] quote missing exit error message

2024-08-25 Thread Anon Loli
Hi list! I am puzzled about this as to why - this has kept on happening to me for many months if not year(s). It has also happened across many different scripts of mine. So upon exit of my scripts, sometimes, and I mean sometimes like 1 out of 20 or so runs of my scripts, it happens. How I ran t

Re: panic - mutex? - AMD64/7.4 to current

2024-08-25 Thread Hugh Graham
On Sun, Aug 25, 2024 at 11:10:19AM +0200, Martin Pieuchot wrote: > On 24/08/24(Sat) 13:14, Hugh Graham wrote: > > On Sat, Aug 24, 2024 at 09:31:43PM +0200, Martin Pieuchot wrote: > > > On 24/08/24(Sat) 12:09, Hugh Graham wrote: > > > > The machine that slowly received the ports tree crashed upon re

Signed integer overflow in telnet.

2024-08-25 Thread Collin Funk
Hi, Earlier this week I committed this change in GNU Inetutils [1]. When sending the 'send dont ' telnet command, the value is not checked for overflow. Likewise for 'do', 'will', 'wont'. Another GNU Inetutils developer segfaults doing 'send dont 2147483648' and 'send dont 9223372034707292160' bu

Re: Signed integer overflow in telnet.

2024-08-25 Thread Theo de Raadt
Noone uses telnet, we (mostly) killed it! https://www.openbsd.org/images/tshirt-9b.jpg There is no way in heck this code is going to be converted in OpenBSD to use strtol(), which is even more willing to eat junk. In our world, someone should adapt this to strtonum(), which is a cynical string t

Re: Signed integer overflow in telnet.

2024-08-25 Thread Collin Funk
"Theo de Raadt" writes: > Noone uses telnet, we (mostly) killed it! > > https://www.openbsd.org/images/tshirt-9b.jpg > > There is no way in heck this code is going to be converted in OpenBSD > to use strtol(), which is even more willing to eat junk. I don't disagree. Especially on the strtol par