Bug 1252087 - Secure memcached installation for overcloud
Summary: Secure memcached installation for overcloud
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Yanis Guenane
QA Contact: Alexander Chuzhoy
URL:
Whiteboard:
Depends On: 1263696 1304473 1304493
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-10 16:48 UTC by Giulio Fidente
Modified: 2023-02-22 23:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1252083
Environment:
Last Closed: 2016-02-03 22:44:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Giulio Fidente 2015-08-10 16:48:19 UTC
Description of problem:
Memcached instances running at overcloud can be accessed by anyone who knows their ips

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-0.8.6-46.el7ost.noarch

Comment 3 Yanis Guenane 2015-09-16 12:43:59 UTC
Based on the project documentation SASL is the mechanism to use to secure the memcached instances.

The memcached package provided in base isn't compiled with SASL support, hence blocking this ticket.

BZ posted https://bugzilla.redhat.com/show_bug.cgi?id=1263696

Comment 4 Mike Burns 2016-02-03 21:56:35 UTC
This can't be fixed without significant work upstream in OpenStack.  The following components in OpenStack use memcached:

keystone
heat
nova
designate
zaqar

None of these currently have support for using a SASL configured memcached.  memcached explicitly disables non-SASL connections when it's running with SASL.  Also, SASL support would require a new python library which we currently don't ship (python-binary-memcached) because the current python-memcached doesn't support binary mode.

Basically, to do this, we need to fix *each* of the above components to be able to use SASL auth with memcached (probably upstream).


Note You need to log in before you can comment on or make changes to this bug.