Ubuntu
juju package

implement full explicit ingress filtering on non-Local provider bootstrapping node

  1. Precise (12.04)
  2. Bug #966590
Bug #966590 reported by Jamie Strandboge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju (Ubuntu)
Triaged
High
Unassigned
Precise
Won't Fix
High
Unassigned
Ubuntu precise-updates

Bug Description

This is a tracking bug for a dependency of the juju MIR (bug #912861).

This is different from bug #966558 in that this bug implements explicit full ingress filtering on the bootstrapping node. This helps ensure that services started on the bootstrapping node can't be trampolined to more privileged juju access. Access might be something like:
 * allow ping and 22/tcp from anywhere
 * allow only ping, 22/tcp and 2181/tcp (zookeeper) from deployed nodes

Jamie Strandboge (jdstrand)
Changed in juju (Ubuntu Precise):
importance: Undecided → High
Clint Byrum (clint-fewbar)
Changed in juju (Ubuntu):
milestone: precise-updates → none
tags: removed: rls-p-tracking
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in juju (Ubuntu Precise):
status: Triaged → Won't Fix
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.