networking-cisco

Time to change https_verify default to True

Bug #1778275 reported by Carol Bouchard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-cisco
Fix Released
Undecided
Carol Bouchard

Bug Description

The https_verify configuration currently defaults to False with the plan to make it True in future release.
Now is the time to take this action to make https certificate verification the default so the connection is secure by default.

Tags: ml2 nexus cisco
Carol Bouchard (caboucha)
Changed in networking-cisco:
assignee: nobody → Carol Bouchard (caboucha)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-cisco (master)

Fix proposed to branch: master
Review: https://review.openstack.org/577868

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-cisco (master)

Reviewed: https://review.openstack.org/577868
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=a17cb8299046d0b777577dcd1745820693511e55
Submitter: Zuul
Branch: master

commit a17cb8299046d0b777577dcd1745820693511e55
Author: Carol Bouchard <email address hidden>
Date: Mon Jun 25 12:40:56 2018 -0400

    Secure Nexus https certificates by default

    In release 5.4.0, the ability to verify https certificates was
    implemented. The default was originally set to False for insecure https
    connections to allow time to acquire certificates. In this release,
    the default is changed to True so certificates will be verified for
    secured connections.

    Change-Id: I23b47e5f616b2522cc687994f2ec35a06e037810
    Closes-bug: #1778275

Changed in networking-cisco:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.