From 66cfb51195b66bae642254f1dc182d88adaf59bb Mon Sep 17 00:00:00 2001 From: gpoirier Date: Sun, 9 Apr 2006 12:45:49 +0000 Subject: [PATCH] Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions + email scrambling using this form: http://www.golivecentral.com/pages/txttut/scramble.shtml (I hope it will be enough not to get too much spam though this link) git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@18062 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/en/bugreports.xml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/DOCS/xml/en/bugreports.xml b/DOCS/xml/en/bugreports.xml index 13af69e387..dd6294eabf 100644 --- a/DOCS/xml/en/bugreports.xml +++ b/DOCS/xml/en/bugreports.xml @@ -11,6 +11,20 @@ receive obscene amounts of email. So while your feedback is crucial in improving that you have to provide all of the information we request and follow the instructions in this document closely. + +Report security releated bugs + +In case you have found an exploitable bug and you would like to do the +right thing and let us fix it before you disclose it, we would be happy +to get your security advisory at +security@mplayerhq.hu. +Please add [SECURITY] or [ADVISORY] in the subject. +Be sure that your report contains complete and detailed analysis of the bug. +Sending a fix is highly appreciated. +Please don't delay your report to write proof-of-concept exploit, you can +send that one with another mail. + + How to fix bugs