Product endorsement in Passwords in Security Guide

Bug #1543249 reported by Rodney Beede
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Expired
Low
Unassigned

Bug Description

The current wording: "Password management applications such as KeePassX and Password Safe can be useful as most support..."

The links to third party products could be construed as an endorsement. No recommendation on specific products should be made but instead the wording changed to something like:

Password management vault technologies are available by third parties (not endorsed by OpenStack) which can be useful as most support the generation of strong passwords and periodic reminders to generate new passwords.

-----------------------------------
Release: 0.0.1 on 2016-02-05 04:39
SHA: f9d3622921bc0f87ee5f71e9ea0fa7940d980fe1
Source: http://git.openstack.org/cgit/openstack/security-doc/tree/security-guide/source/dashboard/passwords.rst
URL: http://docs.openstack.org/security-guide/dashboard/passwords.html

Tags: sec-guide
Revision history for this message
Joseph Robinson (joseph-r-email) wrote :

Patches to the architecture design guide last year also removed third party references. There should be a recommendation in the docs contributor guide about not adding third party references.

Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Low
Chason Chan (chen-xing)
Changed in openstack-manuals:
assignee: nobody → Xing Chen (chen-xing)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to security-doc (master)

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

Revision history for this message
N Dillon (sicarie) wrote :

Is this a confirmed approach by the Docs team?

The original security guide was written to suggest sensible security controls where there exists a gap in OpenStack Tooling. Additionally, this is not the only place 3rd party products are referenced within this guide (dm-verity, logstash, and more to name a few), and in regards to security I believe it is in the best interests of the readers to introduce specific controls as not all are created equal (such as a lack of security around Mozilla's password vault without a master password set).

Changed in openstack-manuals:
status: In Progress → Incomplete
Revision history for this message
Ning Sun (ning-sun) wrote :

as we already found this could be construed as an endorsement, suggest remove it from the Security guide immediately to avoid further burden...

Revision history for this message
N Dillon (sicarie) wrote :

So the 'we' in this case was not done in the security project - this is the first I had heard of this. I'd be interested in the policy of the documentation team here as the recommendations in the guide are supposed to be F/OSS products that address an existing gap in OpenStack tooling. I'd be much more willing to change the language to explicitly state no endorsement is made than remove the recommendations entirely (again, as not all products are as secure as others).

Revision history for this message
Andreas Jaeger (jaegerandi) wrote :

Let's discuss on the docs mailing list, please.

Revision history for this message
Robert Clark (robert-clark) wrote :

I'm not on the docs mailing list so I'll make a comment here. A secure OpenStack deployment cannot be achieved without the correct configuration of under cloud services. The security guide has to mention individual software projects (MySQL, KVM, Xen etc) and it would be farcical to remove them.

While the general principle of no-endorsements makes sense in a more general setting. There is no way we can write this guidance and not mention how to secure specific technologies. Where possible we've chosen 2-3 of the most suitable for OpenStack.

As ND mentions above, not all products in a certain class are created equal. There are for example security considerations to be made between KVM and Xen - or to address this bug specifically, ND gives a great example of why "use a password vault" is bad advice on it's own, there are bad choices out there, this guide exists explicitly to stop people making those bad choices.

Revision history for this message
Rodney Beede (business2008+launchpad) wrote :

So perhaps a general disclaimer at the beginning of the book/documentation that states whether OpenStack endorses or does not endorse specific products in the documentation?

Or perhaps a paragraph in the beginning that states only open source products are referenced in OpenStack documentation.

Would a general disclaimer that no warranty or promise is made by OpenStack that the products (even if open source) have been fully reviewed by OpenStack to not have security bugs?

Probably falls into the OpenStack legal area.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on security-doc (master)

Change abandoned by chen.xing (<email address hidden>) on branch: master
Review: https://review.openstack.org/281117

Chason Chan (chen-xing)
Changed in openstack-manuals:
assignee: Chason (chen-xing) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-manuals because there has been no activity for 60 days.]

Changed in openstack-manuals:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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