diff options
author | Ben Pfaff <blp@nicira.com> | 2015-01-06 10:21:36 -0800 |
---|---|---|
committer | Ben Pfaff <blp@nicira.com> | 2015-01-06 15:20:38 -0800 |
commit | f066424208924681f5ef8fb1e7cb7b33ba74f026 (patch) | |
tree | 475dfca2018fcfd90817a2e29baf2e24dc960d64 /Makefile.am | |
parent | d70e8c28f992c0d8c2918aa0733b935ce1a0caed (diff) | |
download | openvswitch-f066424208924681f5ef8fb1e7cb7b33ba74f026.tar.gz |
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>
Diffstat (limited to 'Makefile.am')
-rw-r--r-- | Makefile.am | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Makefile.am b/Makefile.am index e209e3c7e..6ad6fc2fe 100644 --- a/Makefile.am +++ b/Makefile.am @@ -1,4 +1,4 @@ -# Copyright (C) 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 Nicira, Inc. +# Copyright (C) 2007-2015 Nicira, Inc. # # Copying and distribution of this file, with or without modification, # are permitted in any medium without royalty provided the copyright @@ -89,6 +89,7 @@ docs = \ README-lisp.md \ README-native-tunneling.md \ REPORTING-BUGS.md \ + SECURITY.md \ TODO.md \ WHY-OVS.md EXTRA_DIST = \ |