Re: FreeBSD Security Advisory FreeBSD-SA-19:10.ufs

2019-07-04 Thread CeDeROM
On Thu, Jul 4, 2019, 06:37 Eugene Grosbein wrote: > We should resurrect "early" rc.d script. Its removal in 6.x as opposed to > rewrite was a mistake > as such script is irreplaceable for multiple situations including pretty > ordinary ones > like enabling kernel crashdumps to gmirror. > +1 :-)

Review of FreeBSD Security Advisory Process: Incl Heads Up, Dates, Etc [cont: 5599 SACK}

2019-07-04 Thread grarpamp
Continued from beginnings in: https://lists.freebsd.org/pipermail/freebsd-security/2019-June/009996.html > I don't generally document a timeline of events from our side. There would be benefit to further transparency with some new data fields in FreeBSD advisories, leading to metrics analysis by

?Minor Security Issue - DNS, /etc/hosts, freebsd-update, ?pkg

2019-07-04 Thread Walter Cramer
Suspected severity: Low. Systems with inattentive administrators may not receive the latest updates, and no obvious error messages will point out the problem. Situation discovered in: A few older 11.2-RELEASE FreeBSD systems, with /etc/hosts entries like this: 96.47.72.72 ftp.freebsd.

disable wlan/wifi

2019-07-04 Thread Lucas Nali de Magalhães
Hi. I started a bug report to request a way to disable wlan/wifi but I think I'm better writing here first: my inability to disable wlan/wifi is becoming a security issue for me here (I'm still learning how to use the Bugzilla web interface). Long story short: wifi never goes away. Please help

Re: Review of FreeBSD Security Advisory Process: Incl Heads Up, Dates, Etc [cont: 5599 SACK}

2019-07-04 Thread Peter Jeremy
On 2019-Jul-04 00:06:10 -0400, grarpamp wrote: >Continued from beginnings in: >https://lists.freebsd.org/pipermail/freebsd-security/2019-June/009996.html > >> I don't generally document a timeline of events from our side. > >There would be benefit to further transparency with >some new data fields