Re: FreeBSD Security Advisory FreeBSD-SA-23:02.openssh

2023-02-18 Thread void
Hi, On Fri, 17 Feb 2023, at 13:28, Trond Endrestøl wrote: > On Thu, 16 Feb 2023 19:47+0100, Michael Grimm wrote: > >> > On 16. Feb 2023, at 19:23, FreeBSD Security Advisories >> > wrote: >> >> […] >> >> > Branch/path Hash Revision >> > -

Re: 45 vulnerable ports unreported in VuXML

2023-04-04 Thread void
On Sun, Mar 26, 2023 at 12:16:53PM +0200, Hubert Tournier wrote: Hello, While working on pipinfo , an alternative Python packages management tool, I noticed that some Python packages installed as FreeBSD ports where marked as vulnerable by the Python Packaging

Re: Downfall microcode update

2023-08-09 Thread void
On Wed, Aug 09, 2023 at 11:46:10AM +0200, Dag-Erling Smørgrav wrote: Eugene Grosbein writes: cpupdate_enable="YES" # in /etc/rc.conf should be enough You mean microcode_update_enable="yes" DES What's the proper way then, for intel? 1. install sysutils/cpupdate and enable it in rc.conf ?

securelevel 1

2023-10-24 Thread void
Hi, I'd like to set append-only on an arm64 system running stable/14-n265566 (so securelevel=1) but how would newsyslog(8) handle it? How will it rotate logs? --

Re: securelevel 1

2023-10-24 Thread void
On Tue, 24 Oct 2023, at 11:31, Miroslav Lachman wrote: > root@neon ~/ # find -s -x / -flags +schg,sappnd > /.sujournal > /lib/libc.so.7 > /lib/libcrypt.so.5 > /lib/libthr.so.3 > /libexec/ld-elf.so.1 > /libexec/ld-elf32.so.1 > /sbin/init > /usr/bin/chpass > /usr/bin/crontab > /usr/bin/login > /usr/

Re: securelevel 1

2023-10-24 Thread void
On Tue, 24 Oct 2023, at 17:45, Cy Schubert wrote: > What a lot of large enterprises do is send logs off machine. A *.* log to > @IP or an agent does the same thing. The remote logging server also has > software to allow one to search the logs for a machine or multiple machines > allowing one to

Re: securelevel 1

2023-10-26 Thread void
On Thu, Oct 26, 2023 at 11:36:22PM +0200, Dag-Erling Smørgrav wrote: void writes: In order to accomplish what I'd like, I understand that I'd need to set +schg on the individual logs, then set the securelevel afterwards and reboot. If you set the log file +schg, it can't be wr