Blog

Comments

• 

  #1 Christof Damian said on the 2012/12/18 at 22:12
  It might be good also to mention the CVE number where available. These are for used for example in Linux distributions to track security issues.
  
  There are some already available for symfony: http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=symfony
  
  It could be even an idea to request numbers for new security issues which haven't a assigned one yet, but I have no idea how complicated that is.
• 

  #2 Lukas Kahwe Smith said on the 2012/12/18 at 23:55
  The next important step here is to better formalize the security team, especially integrate members of our big users like Drupal and ezPublish.
• 

  #3 Fabien Potencier said on the 2012/12/19 at 08:24
  I've just added references to CVE numbers where available:
  
  https://github.com/symfony/symfony-docs/pull/2047
• 

  #4 Fabien Potencier said on the 2012/12/19 at 08:33
  I've just sent an email to learn more about the process of CVE identifiers management as I would like to get one for each new security issue in the future.