dlitz
Joined 15 years ago
Joined 15 years ago
The concern for me is has been the accounts of far more directly-relevant behaviour, such as (iirc):
* repeated phone calls to someone from different phone numbers
* leering
* breaking the ground rules for an event, and justifying it on the basis that he's personally exempt from any rules
* singling out a teenage girl attending one of his talks (as in "oh wow, a GIRL")
* single her out again while telling his questionable 'EMACS virgins' joke
* saying in an interview that he didn't know any women who have contributed to GCC, when there had been at least 4
It all adds up to several accounts of people saying they've left the free software movement (or avoided it entirely) because of his behaviour combined with his stature. As a community leader who supposedly leads by example, he needs to do better, and if he doesn't, the community needs to hold him accountable. That's happening now.Personally, I think this is a good thing, and I'm glad that he's made the decision to step aside (even if under pressure) rather than fight bitterly and see the community divide along these lines.
It also seems like a good opportunity for him to pass the torch and see what happens, or at least take a long hiatus to get some caring advice and to sort himself out, like Linus did last year. The FSF will eventually need to become an institution that can carry on its mission without him, and this will be a good test of that. If things go off the rails, he can pen another manifesto and I'm sure a bunch of us will read it.
Installing known-vulnerable old versions of legitimate software can be just as bad as installing custom malware.
Nowadays, it's arguably a best-practice when designing a new protocol or storage format to simply make all checksums cryptographically strong unless there's a reason not to. I think that might be where the confusion is coming from.
http://pmprb-cepmb.gc.ca/about-us/frequently-asked-questions
I found this was the case (with Telus) until I reconfigured the DHCPv6-PD client on my gateway, mainly to stop it from sending DHCPv6 Release messages and to have it explicitly request the prefix I was previously assigned.
OpenWRT in particular seemed to be built not to save any dhcp client state in non-volatile memory, resulting in a lot of unnecessary address and prefix churn when rebooting the router. I've had the same stable prefix for over a year now, using systemd-networkd with the following configuration (the important parts are SendRelease=no, RequestAddress= and PrefixDelegationHint=; the rest of the options are just insurance):
https://gist.github.com/dlitz/487d733140aa784559d73e4cd6f723...