Re: Should FUSE mounts be considered local?

2022-04-23 Thread Allan Streib
On Sat, Apr 23, 2022, at 8:51 AM, Stuart Henderson wrote: > I don't know if there's a way to indicate network/not with fuse (and even if > there is on other OS, the implementation on OpenBSD is not full featured). > Certainly some fuse filesystem types would want to be considered local > (ntfs-3g

Re: No valid root disk found when upgrading

2022-04-23 Thread michal . lyszczek
On 2022-04-22 07:56:25, Stuart Henderson wrote: > On 2022-04-21, Stuart Henderson wrote: > >> upgrade# cd /dev; sh MAKEDEV sd0 > >> upgrade# mount -t ffs -r /dev/sd0a /mnt > >> upgrade# ls /mnt > >> .cshrc bsd dev sbin > >> .profile

Re: Should FUSE mounts be considered local?

2022-04-23 Thread Stuart Henderson
On 2022-04-22, Allan Streib wrote: > I had an SMB network share mounted on a directory under my $HOME (via > FUSE using usmb package), and overnight security(8) tried to check it for > setuid/setgid files. That did not go well. I see that I could have set > the SUIDSKIP environment variable but I

Re: kernel fault after 7.1

2022-04-23 Thread Stuart Henderson
On 2022-04-23, kasak wrote: > hello everybody. after upgrading to 7.1 my router started to panic very > often :(( about twice a day. Please report to b...@openbsd.org, with the information from your mail, plus dmesg, and an outline of how the machine is configured (what types of network

Re: 7.1 & nsd - failed writing to tcp: Permission denied

2022-04-23 Thread Stuart Henderson
On 2022-04-22, Laura Smith wrote: > --- Original Message --- > On Friday, April 22nd, 2022 at 18:16, Peter J. Philipp > wrote: > >> So that's weird becuase the 3-way handshake must have completed for nsd to >> reply a query. Meaning there was SYN's and ACK's being exchanged but perhaps

syspatch brought system to 7.1-stable (was Re: Sprurios errors from syspatch -c)

2022-04-23 Thread Marc Peters
On Fri, Apr 22, 2022 at 08:51:43PM -0600, Theo de Raadt wrote: > And of course, the syspatch testing procedures will get another step or > two to make sure this doesn't happen again > > So just wait. Thank you for explanation and clarification. Two of my systems were already hit by that