On Wed, Jan 07, 2015 at 12:17:45AM +0100, Thomas Graf wrote: > On 01/06/15 at 10:22am, Ben Pfaff wrote: > > 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 <b...@nicira.com> > > Reviewed-by: Flavio Leitner <f...@redhat.com> > > Looks perfect to me to ensure we are well prepared. We can revise as > needed when we handle the first case. > > Acked-by: Thomas Graf <tg...@noironetworks.com>
I agree. That's three acks or reviews, good enough for me. I applied this to master. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
