yahoo-eng-team team mailing list archive

[Adam Harwell <flux.adam@xxxxxxxxx>]

Public bug reported:

The current workflow for TLS Termination on loadbalancers has a couple
of interesting security vulnerabilities that need to be addressed
somehow. The solution I propose is to encourage the use of passphrase
encryption on private keys, and to store that passphrase in Neutron-
LBaaS along with the Barbican href, instead of inside Barbican.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

** Description changed:

- The current workflow for TLS Termination on loadbalancers has a couple of
- interesting security vulnerabilities that need to be addressed somehow. The
- solution I propose is to encourage the use of passphrase encryption on private
- keys, and to store that passphrase in Neutron-LBaaS along with the Barbican
- href, instead of inside Barbican.
+ The current workflow for TLS Termination on loadbalancers has a couple
+ of interesting security vulnerabilities that need to be addressed
+ somehow. The solution I propose is to encourage the use of passphrase
+ encryption on private keys, and to store that passphrase in Neutron-
+ LBaaS along with the Barbican href, instead of inside Barbican.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1508243

Title:
  Store Private Key Passphrase in Neutron-LBaaS for TLS Terminations

Status in neutron:
  New

Bug description:
  The current workflow for TLS Termination on loadbalancers has a couple
  of interesting security vulnerabilities that need to be addressed
  somehow. The solution I propose is to encourage the use of passphrase
  encryption on private keys, and to store that passphrase in Neutron-
  LBaaS along with the Barbican href, instead of inside Barbican.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1508243/+subscriptions