-
-
Replying to @doragasu
Calling djb incompetent are words too big for almost anyone. Careful there!
1 reply 0 retweets 1 like -
Replying to @reidrac
I do not know this exact case. But I fight everyday people that are in a high position because of their expertise in one field, and want to impose nonsense on other fields they think they know, but they don't. Very frustrating and energy consuming experience.
1 reply 0 retweets 0 likes -
Replying to @doragasu
IDK. djb can be eccentric, incompetent? uh https://en.wikipedia.org/wiki/Daniel_J._Bernstein …
1 reply 0 retweets 0 likes -
Yes, I specified incompetent *in another field*. Not checking for integer overflows and relying on your program being run with a virtual memory limit for security instead is incompetence in the field of secure service programming. Sure, I trust him to write crypto code though.
2 replies 0 retweets 0 likes -
Not sure if that's the context though. https://en.wikipedia.org/wiki/Qmail#Security_reward_and_Georgi_Guninski's_vulnerability … IMHO djb knows what's going on, this is always been about the reward.
1 reply 0 retweets 0 likes -
If he knew what was going on he'd have fixed the bug 15 years ago, even if he declined to reward. The fact that he didn't fix it makes him incompetent and his software dangerous to run. If he had declined to reward only then he'd only be a bit of a dick :)
1 reply 0 retweets 0 likes
BTW, qmail and djb in this context are also a perfect example of failing to keep up with the times. Yes, when qmail came out, its competition was sendmail, and qmail was a big step up in security. But our standards have improved, and qmail hasn't.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.