The emotionally loaded name suggests that it is the most responsible way to conduct vulnerability research

Ormandy was one of seven members of the Google security team contributing to a blog post calling for a new look at responsible disclosure and deadlines on firms to sort out flaws.

Google said resonsible disclosure - alerting companies to flaws before taking them public - is not necessarily always more "responsible" than full disclosure, which is publishing the vulnerability without warning.

"The emotionally loaded name suggests that it is the most responsible way to conduct vulnerability research - but if we define being responsible as doing whatever it best takes to make end users safer, we will find a disconnect," the post noted.

"We’ve seen an increase in vendors invoking the principles of 'responsible' disclosure to delay fixing vulnerabilities indefinitely, sometimes for years; in that timeframe, these flaws are often rediscovered and used by rogue parties using the same tools and methodologies used by ethical researchers," it added.

60 days to disclosure

Calling for software vendors to act responsibly too, Google said most critical bugs could be fixed within 60 days. "In our opinion, this small tweak to the rules of engagement will result in greater overall safety for users of the internet," the post said.

Google said its own security researchers find flaws in software from "a variety of vendors", and will support them if they publish flaws after giving companies a fair deadline to deal with the issue. It also said some flaws will need more "aggressive" deadlines if hackers are already aware of them.

The web giant admitted it would need to live by such rules itself, and had previously missed disclosure deadlines. In such cases, it's been "happy for publication to proceed, and grateful for the heads-up."