SECURITY: New document describing proposed security process for OVS.
authorBen Pfaff <blp@nicira.com>
Tue, 6 Jan 2015 18:21:36 +0000 (10:21 -0800)
committerBen Pfaff <blp@nicira.com>
Tue, 6 Jan 2015 23:20:38 +0000 (15:20 -0800)
commitf066424208924681f5ef8fb1e7cb7b33ba74f026
tree475dfca2018fcfd90817a2e29baf2e24dc960d64
parentd70e8c28f992c0d8c2918aa0733b935ce1a0caed
SECURITY: New document describing proposed security process for OVS.

Open vSwitch needs some kind of process for handling vulnerabilities.  So
far, we've been pretty lucky that way, but it can't last forever, and I
think we'll be better off if we have at least the outline of an established
process whenever a significant vulnerability comes along.  Here's my draft
of a process based on the documentation of the OpenStack process at
https://wiki.openstack.org/wiki/Vulnerability_Management.

I don't have a lot of experience with this kind of thing myself, so I'd
appreciate critical review from anyone who does.

Signed-off-by: Ben Pfaff <blp@nicira.com>
Reviewed-by: Flavio Leitner <fbl@redhat.com>
Acked-by: Justin Pettit <jpettit@nicira.com>
Acked-by: Thomas Graf <tgraf@noironetworks.com>
Makefile.am
REPORTING-BUGS.md
SECURITY.md [new file with mode: 0644]