Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN4PR11MB0882F9FE65C1607B1F2A45BDAAEC0@BN4PR11MB0882.namprd11.prod.outlook.com>
Date: Mon, 22 Jan 2018 17:20:36 +0000
From: Mikhail Utin <mikhailutin@...mail.com>
To: "oss-security@...ts.openwall.com" <oss-security@...ts.openwall.com>
Subject: Re: How to deal with reporters who don't want their
 bugs fixed?

 r.hering@....de <r.hering@....de> wrote:


Keeping it individual without public announced maximum embargo time would
also help prevent folks from jumping to 0daying everything per default:)


However, to me it is pure "Security by Obscurity" in a bit different wording. It never worked. Simply think that somebody else knows the secret and with your help continues using that.


"hiding intention for fame / paper publications / product selling" Hiding is not good. We are not monks and Security is not our God. Things like publications and selling require time and actually help to move things forward.


Mikhail Utin, CISSP


________________________________
From: r.hering@....de <r.hering@....de>
Sent: Monday, January 22, 2018 05:49
To: oss-security@...ts.openwall.com
Subject: Re: [oss-security] How to deal with reporters who don't want their bugs fixed?

Point is, many "security researchers" overly pretend to work for security
hiding intention for fame / paper publications / product selling.

Accept unnecessary long embargoes then you support this behaviour but
might provide patches faster after public release.
Reject unnecessary long embargoes then you discourage this behaviour but
might provide patches slower after public release next time.

I think the decision is always individual per vulnerability weighting how
grave/easy to find/abuse it is vs. how interested you are in future early
reports.
Keeping it individual without public announced maximum embargo time would
also help prevent folks from jumping to 0daying everything per default:)

(°X|

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.