hello everybody. after upgrading to 7.1 my router started to panic very
often :(( about twice a day.
This is the information from the screen:
kernel: protection fault trap, code=0
Stopped at ipsp_ids_gc+0xb4 cmpl $0,0x64(%r14)
ddb{0}> show panic
the kernel did not panic
ddb{0}> trace
Richard Narron wrote:
> On Fri, 22 Apr 2022, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
>
> > After the 7.1 update syspatch -c started throwing errors due to a
> > missing signatures file:
> >
> > Patch check:
> > syspatch: Error retrieving
> >
On Fri, 22 Apr 2022, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> After the 7.1 update syspatch -c started throwing errors due to a
> missing signatures file:
>
> Patch check:
> syspatch: Error retrieving
> http://ftp.openbsd.org/pub/OpenBSD/syspatch/7.1/amd64/SHA256.sig: 404 Not
> Found
>
>
Ingo Schwarze writes:
> That's not new, it has been like that for at least 14 years and likely
> much longer:
Heh :-) Filing a bug report about my horrible memory seems wrong.
> I don't think adding the more characters to each line would be a good idea.
> It would cause line wrapping in mail
If anyone is interested have a small go clone of the httpd web server
here: https://github.com/aaronriekenberg/go-httpd
Not nearly as complete as the real httpd but has enough features to
roughly handle a config similar to /etc/examples/httpd.conf
Sample config file:
Hi Lyndon,
Lyndon Nerenberg wrote on Fri, Apr 22, 2022 at 09:33:57AM -0700:
> In the output from the daily insecurity report run, the sections on
> setuid and block device changes are missing any diff markup. The
> remaining sections are fine.
>
> From this morning's post-7.1-upgrade run:
>
>
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 didn't think about that in advance
and even
Laura, for a first step I would look at pflog(4). As Peter hinted,
if you have an obscure pf rule blocking things after the connection
sets up, this will point it out. (Make sure you have all the
appropriate pflog bits enabled, of course.)
If that doesn't work your next step is to fire up
On Fri, Apr 22, 2022 at 04:03:17PM +, Laura Smith wrote:
> Hi,
> Am seeing some odd nsd log entries crop up in /var/log/messages.?? Any cause
> for concern ? Anyone else seen these ?
>
> Apr 22 15:08:46 nsd[99760]: failed writing to tcp: Permission denied
>
> No problems with IPv4 or IPv6
In the output from the daily insecurity report run, the sections on
setuid and block device changes are missing any diff markup. The
remaining sections are fine.
>From this morning's post-7.1-upgrade run:
Setuid changes:
-r-sr-xr-x 2 root bin 355952 Sep 30 13:01:03 2021 /sbin/ping
After the 7.1 update syspatch -c started throwing errors due to a
missing signatures file:
Patch check:
syspatch: Error retrieving
http://ftp.openbsd.org/pub/OpenBSD/syspatch/7.1/amd64/SHA256.sig: 404 Not Found
The error is valid. To suppress this message it would make sense to drop
an
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
>> .profilebsd.booted etc sys
>> altroot
12 matches
Mail list logo
