SECURITY 2.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061
  1. Security Policy
  2. ===============
  3. To report a vulnerability see "Reporting a Vulnerability" below.
  4. Security Incident Policy
  5. ========================
  6. Security bug reports are treated with special attention and are handled
  7. differently from normal bugs. In particular, security sensitive bugs are not
  8. handled in public but in private. Information about the bug and access to it
  9. is restricted to people in the security group, the individual engineers that
  10. work on fixing it, and any other person who needs to be involved for organisational
  11. reasons. The process is handled by the security team, which decides on the people
  12. involved in order to fix the issue. It is also guaranteed that the person reporting
  13. the issue has visibility into the process of fixing it. Any security issue gets
  14. prioritized according to its security rating. The issue is opened up to the public
  15. in coordination with the release schedule and the reporter.
  16. Disclosure Policy
  17. =================
  18. Everyone involved in the handling of a security issue - including the reporter -
  19. is required to adhere to the following policy. Any information related to
  20. a security issue must be treated as confidential and only shared with trusted
  21. partners if necessary, for example to coordinate a release or manage exposure
  22. of clients to the issue. No information must be disclosed to the public before
  23. the embargo ends. The embargo time is agreed upon by all involved parties. It
  24. should be as short as possible without putting any users at risk.
  25. Supported Versions
  26. ==================
  27. Only the most recent version of the GRUB is supported.
  28. Reporting a Vulnerability
  29. =========================
  30. The security report should be encrypted with the PGP keys and sent to ALL email
  31. addresses listed below. Every vulnerability report will be assessed within
  32. 72 hours of receiving it. If the outcome of the assessment is that the report
  33. describes a security issue, the report will be transferred into an issue on the
  34. internal vulnerability project for further processing. The reporter is updated
  35. on each step of the process.
  36. While there's currently no bug bounty program we appreciate every report.
  37. * Contact: Daniel Kiper <daniel.kiper@oracle.com> and
  38. Daniel Kiper <dkiper@net-space.pl>
  39. * PGP Key Fingerprint: BE5C 2320 9ACD DACE B20D B0A2 8C81 89F1 988C 2166
  40. * Contact: Alex Burmashev <alexander.burmashev@oracle.com>
  41. * PGP Key Fingerprint: 50A4 EC06 EF7E B84D 67E0 3BB6 2AE2 C87E 28EF 2E6E
  42. * Contact: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
  43. * PGP Key Fingerprint: E53D 497F 3FA4 2AD8 C9B4 D1E8 35A9 3B74 E82E 4209