OpenStack Compute (Nova)

nova-vncproxy's flash socket policy port is not configurable

Reported by Ewan Mellor on 2011-11-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Ewan Mellor

Bug Description

nova-vncproxy's flash socket policy port is not configurable. It's hardcoded as 843. This makes it difficult to run an unprivileged nova-vncproxy (say with a port-mapping load balancer in front of it) because the unprivileged user can't bind a low-numbered port.

Ewan Mellor (ewanmellor) wrote :
Changed in nova:
status: New → In Progress
assignee: nobody → Ewan Mellor (ewanmellor)

Reviewed: https://review.openstack.org/1912
Committed: http://github.com/openstack/nova/commit/43214c6e99bb010b781e17b9c3acbe2c12f29672
Submitter: Jenkins
Branch: master

 status fixcommitted
 done

commit 43214c6e99bb010b781e17b9c3acbe2c12f29672
Author: Ewan Mellor <email address hidden>
Date: Sun Nov 27 14:48:37 2011 -0800

    Bug #896997: nova-vncproxy's flash socket policy port is not configurable

    Add flags called vncproxy_flash_socket_policy_port and
    vncproxy_flash_socket_policy_host, to allow the admin to configure
    the Flash socket policy listener.

    Change-Id: If42839ccd86f1c8723221049d7c76b6f5ad0aa2d

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2011-12-14
Changed in nova:
milestone: none → essex-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-2 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers