3 ms·
Some interesting commentary: https://news.ycombinator.com/item?id=14010010 https://news.ycombinator.com/item?id=14010010 https://news.ycombinator.com/item?id=
by FireBeyond 7y ago
Some interesting commentary:
https://news.ycombinator.com/item?id=14010010 https://news.ycombinator.com/item?id=14010010
https://news.ycombinator.com/item?id=12308246 https://news.ycombinator.com/item?id=12308246
> That may feel good to say, but as someone whose job it was to find these kinds of bugs in software from companies ranging from tiny startups to financial exchanges to major tech vendors, this is a kind of carelessness shared by virtually everyone shipping any kind of software anywhere.
> That said, the term "responsible disclosure" is Orwellian, and you should very much avoid using it.
> It's coercive. It redefines language to make any handling of vulnerabilities not condoned by the vendors who shipped those vulnerabilities "irresponsible", despite the fact that third parties who discover vulnerabilities have no formal duty to cooperate with those vendors whatsoever.
> The better term is "coordinated disclosure". But uncoordinated disclosure is not intrinsically irresponsible. For instance: if you know there's an exploit in the wild for something, perhaps go ahead and tweet the vulnerability without notice!
- wahern 7y ago> That said, the term "responsible disclosure" is Orwellian, and you should very much avoid using it. It seems you disapprove of the phrase "responsible disclosure" because it's ambiguous and can be used as a cudgel. That's no different than the term "Orwellian", which is ambiguous and can be used as a cudgel. All people are saying is that it's better to give the vendor a heads up before releasing an exploit. Maybe they have something to tell you that might cause you to delay; maybe not. Surely responsible disclosure implies to most people some amount of due diligence in choosing a timeline for disclosure. If you don't give a vendor any opportunity to discuss, there's been no such due diligence on your part.
- ryanlol 7y ago>It seems you disapprove of the phrase "responsible disclosure" because it's ambiguous and can be used as a cudgel This is like saying that a glock can be used as a weapon. Yes, it was carefully designed to be one. >We must secure the existence of our people and a future for white children This might also be ambiguous, but we all understand the genocidal connotations.
- cyphar 7y ago> This might also be ambiguous, but we all understand the genocidal connotations. Ah yes, because using the term "responsible disclosure" is very clearly analogous to being a white supremacist. There's no need to be so ridiculously dramatic -- "responsible disclosure" was objectively the term-du-jour used by the infosec community until fairly recently. And it's perfectly understandable why the community changed their mind (vendors started co-opting the phrase as a method of shaming researchers for doing the right thing), but you are shooting yourself in the foot by being so aggressive about it. Why not just say "we used to use that term, but we use this other term now because of the following reasons"?
- ryanlol 7y agoYou've got the order of events wrong here. The term "responsible disclosure" originated from the legal teams of vendors around 2002, it was never co-opted by vendors. Here's a little historical context https://www.securityfocus.com/columnists/120 https://www.securityfocus.com/columnists/120 I think the 14 words comparison is apt. Without context there's nothing obviously wrong with the 14 words, just like there's nothing obviously wrong with "responsible disclosure".
- kortilla 7y agotptacek is just trying to speak from a position of authority, there is no substance to his argument. The position is that it’s a term used by vendors... therefore bad? I’ve already pointed out there is an entire academic subfield to infosec that uses the term that has no financial incentive like a vendor. Releasing anything that can be used to harm the public has ethical implications, period. There is no grey area there. Responsible disclosure is entirely about minimizing impact. People that don’t like the term don’t like it because they don’t like the idea that there are ethical implications for releasing information. Do you think there is an ethical gray area to releasing a method to the public to gain access to the secure side of an airport terminal without going through security so guns/bombs can be brought in undetected? What if that method is a software vulnerability in the door locks they use? > The better term is "coordinated disclosure". But uncoordinated disclosure is not intrinsically irresponsible. For instance: if you know there's an exploit in the wild for something, perhaps go ahead and tweet the vulnerability without notice! FFS, that’s why the term is “responsible disclosure” and not “coordinated disclosure”. Responsible disclosure is the entire process of determining when and how to inform vendors and/or major users or if to inform them at all. Responsible disclosure is entirely about doing disclosure in the least harming way possible to the public.