4 ms·
What exactly do you mean by "full disclosure" here? If you mean disclosure of zero days with no warning, then yes, generally responsible disclosure is more desi
by nl 9y ago
What exactly do you mean by "full disclosure" here? If you mean disclosure of zero days with no warning, then yes, generally responsible disclosure is more desirable. I'm not aware of any security professional who disagrees with this stance.
- sneak 9y agoI am a security professional who thinks full and immediate disclosure is always responsible and professional and desirable.
- sneak 9y agoExample: Today, I found out that on the close order of a thousand people at Yubikey, Infineon, Microsoft, Google, Lenovo, and Fujitsu knew that my Yubikey’s RSA keys were weak—IN FEBRUARY. I found out today. Two legs good. Four legs bad. Post that shit to the mailing list. There are far more good people than bad people. Stop covering for the fact that huge corporations are risk-averse and slow to make changes; that’s baking bias into the process.
- nl 9y agoI don't think anyone would (or should!) argue that 9 months delay is responsible disclosure. If they do then they are wrong. But dumping zero days isn't any better. This 2003 paper from SANS[1] talks about the BugTrac policy of full disclosure after 14 days, but says most recommend 30 days. I think that is a reasonable expectation. [1] https://www.sans.org/reading-room/whitepapers/threats/define-responsible-disclosure-932 https://www.sans.org/reading-room/whitepapers/threats/define...
- sneak 9y agoAll those companies argued that for the last 9 months they sat on the Yubikey vuln key issue.