Can someone explain what this will impact in normal use? Does this mean that
passwords will default to DES? I've dug around a little and I'm not seeing
where a default is set for passwords - my desktop right now is using sha512,
but if I had to guess I'd say it's because it was the crypt(3) default
On Wed, Oct 22, 2014 at 09:58:01AM -0400, Mason Loring Bliss wrote:
> my desktop right now is using sha512, but if I had to guess I'd say it's
> because it was the crypt(3) default.
Or I could look at login.conf and see that it's set to sha512 there.
Never mind. Nothing to
On Wed, Oct 22, 2014 at 09:08:31PM +0200, Dag-Erling Smørgrav wrote:
> See https://bugs.freebsd.org/192277 for details and examples of affected
> applications.
Ah, thank you. That sheds a lot more light on it.
--
Mason Loring Bliss ma...@blisses.org Ewige Blumenkraft!
kages found.
--
Mason Loring Bliss ma...@blisses.orgEwige Blumenkraft!
(if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scene I
___
freebsd-security@freebsd.org mailing list
https://lists.freebsd.o
On Thu, Aug 13, 2015 at 04:20:08PM -0400, Mason Loring Bliss wrote:
> subversion-1.8.10_3 is vulnerable:
To clarify, I had this one artificially held back. The up to date quarterly
package vulnerability list for Subversion looks like this:
subversion-1.8.13_2 is vulnerable:
subvers
quarterly branches, because I think it's a great
idea generally. Falling back to the high-churn option to get access to
security patches when what you want is a stable environment is an awful idea.
I'm hoping that we do this, but do it right. I can't see how anyone could
find fault with
m sincerely, deeply grateful that the high-
profile stuff I pointed out was fixed so rapidly in response to my pointing
it out.
--
Mason Loring Bliss (( If I have not seen as far as others, it is because
ma...@blisses.org )) giants were standing on my shoulders. - Hal Abelson
_
