Re: FreeBSD Security Advisory FreeBSD-SA-20:31.icmp6

2020-12-10 Thread Mark Johnston
On Wed, Dec 09, 2020 at 03:45:13PM +, Wall, Stephen wrote: > This advisory states "Systems with IPv6 disabled are not affected." What > constitutes disabling IPv6 in this context? Would it require disabling it > when building the kernel, or is `ipv6_enable="NO"` in `rc.conf` sufficient? Th

Re: FreeBSD Security Advisory FreeBSD-SA-20:32.rtsold

2020-12-10 Thread Mark Johnston
On Wed, Dec 09, 2020 at 03:29:39PM +, Wall, Stephen wrote: > Regarding FreeBSD-SA-20:32.rtsold, does this line indicate that the messages > must come from directly connected equipment, or could it come through a hub > or router as well? > > > Note that rtsold(8) only processes messages recei

Re: FreeBSD Security Advisory FreeBSD-SA-20:13.libalias

2020-05-12 Thread Mark Johnston
On Tue, May 12, 2020 at 07:44:31PM +, FreeBSD Security Advisories wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > = > FreeBSD-SA-20:13.libalias Security Advisory >

Re: FreeBSD Security Advisory FreeBSD-SA-19:23.midi

2019-08-20 Thread Mark Johnston
On Tue, Aug 20, 2019 at 04:01:39PM -0600, Ian Lepore wrote: > On Wed, 2019-08-21 at 04:55 +0700, Eugene Grosbein wrote: > > 21.08.2019 3:12, FreeBSD Security Advisories wrote: > > > > [skip] > > > > > IV. Workaround > > > > > > No workaround is available. Custom kernels without "device sound"

Re: FreeBSD Security Advisory FreeBSD-SA-19:11.cd_ioctl

2019-07-03 Thread Mark Johnston
On Tue, Jul 02, 2019 at 06:55:26PM -0700, Ronald F. Guilmette wrote: > In message <20190703004928.576ca1a...@freefall.freebsd.org>, > freebsd-security@freebsd.org wrote: > > >Topic: Privilege escalation in cd(4) driver > >... > >devfs.conf(5) and devfs.rules(5) can be used to remove read

Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-19:07.mds

2019-05-15 Thread Mark Johnston
On Wed, May 15, 2019 at 09:33:50AM -0500, Kyle Evans wrote: > On Wed, May 15, 2019 at 8:33 AM mike tancsa wrote: > > > > On 5/15/2019 8:18 AM, Wall, Stephen wrote: > > >> New CPU microcode may be available in a BIOS update from your system > > >> vendor, > > >> or by installing the devcpu-data pa