On 01/14/2013 01:56 PM, Justin Clift wrote:
On 10/01/2013, at 4:17 PM, Tomas Sedovic wrote:
> While it's in spirit of free and open source software to publicly report
> bugs as soon as they're discovered, it's not the best thing to do with
> security vulnerabilities.
> The common practice between security researchers is to notify the
> developers in confidence, give them a reasonable time to fix the bug and
> then release the details to public. This is called "responsible
> It helps to minimise the risks of actual exploits happening.
> We have a specific process for reporting security-related issues,
> documented on our Contact Us page:
> In essence:
> 1. Send security vulnerabilities here: aeolus-security(a)fedorahosted.org
> 2. if you want, GPG-encrypt the email using our public key:
> Please keep this in mind when you discover a new security issue. It will
> only become more serious as our user base and downstream grows.
Interestingly, that link is to the old website (which last I heard
shouldn't be online any more?).
The new website contact page is here:
Thanks for pointing it out, I must have missed that.
Most of the security related stuff was removed to make things simpler.
I added it back *and* made security a separate section ;-)
The security contact was almost impossible to find after the
simplification and the link to our GPG key was missing.
We do *not* want to have zero days appear on aeolus-devel or someone's
blog because they couldn't find the way to report it to us securely.
I'm all for simplicity, but this info needs to be there and easy to find.
Aeolus Cloud Evangelist