another day, another set of ntp vulnerabilities fixed in freebsd
I am amused by this phrasing in the advisory: '...an optional 4th field in the ntp.keys file to specify which IPs can serve time...'
Seriously guys, are we not doing phrasing anymore?
I suppose IPs assigned to a jail can be said to be "serving time"
sadly, freebsd-update is somewhat borked
oh?  I hadn't gotten as far as trying to apply the patches.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209147
anyway, I'm using openntpd on most freebsd installs, so not a big deal
sjackso: freebsd 10.3 updates are broken too
oh dn mentioned it
dne even
ahh dne managed to even find an official bug report about it
yup, saw it on two 10.3 installs so figured I wasn't alone :)
yeah, i found other reports, just not an official bug.  it does seem recent though.
and i asked on #freebsd
and then someone else came in saying that they were experincing it
in of itself it's not a big deal, but the fact that there's yet another -release broken in quite a bad way is just ick
the other one that was broken would make the file system need a fsck after a fresh install/update
I'd say it's likely the problem is in how the freebsd-updates are built/distributed and not in 10.3 itself
ahh so it may be able to be fixed without needing to change the binaries?
possibly, but I'm just speculating :)
i wonder when freebsd 11 is coming out
apparently it should come out around september
BryceBot: no
Oh, okay... I'm sorry. 'I dropped the ball there'
oh snap BryceBot that was actually a good one, but where did that come from? Your twss is supposed to be channel-specific... :/
I hear you.  I was going to be installing a new system today.. perhaps it'll be on 10.2 for a bit.
My excuse is just being too busy with a move to have installed 10.3. But if it aint broke, then...
s/installed/upgraded to/
<brycec> My excuse is just being too busy with a move to have upgraded to 10.3. But if it aint broke, then...