The activex needs a new "Proxy" property to configure the client proxy via controller. The patch is already in upstream, and it will be release with client update. the bug is just for.. tracking.
(In reply to comment #0) > The activex needs a new "Proxy" property to configure the client proxy via > controller. > > The patch is already in upstream, and it will be release with client update. > the bug is just for.. tracking. Hi, What is the property name? I assume only string passed from RHEVM without any validation is sent to client controller, correct? Thanks.
(In reply to comment #1) > (In reply to comment #0) > > The activex needs a new "Proxy" property to configure the client proxy via > > controller. > > > > The patch is already in upstream, and it will be release with client update. > > the bug is just for.. tracking. > > Hi, > What is the property name? I assume only string passed from RHEVM without > any validation is sent to client controller, correct? > Thanks. property name is "Proxy", it's a string with the same content description as environment variable or the virt-viewer configuration file. Also described in spice-protocol: The value must be of the form [protocol://]<host>[:port] The proxy string may be specified with a protocol:// prefix to specify alternative proxy protocols. If no protocol is specified in the proxy string or if the string doesn't match a supported one, the proxy will be treated as a HTTP proxy.
(In reply to comment #2) > > The value must be of the form [protocol://]<host>[:port] > > The proxy string may be specified with a protocol:// prefix to specify > alternative proxy protocols. > > If no protocol is specified in the proxy string or if the string > doesn't match a supported one, the proxy will be treated as a HTTP > proxy. If no port is specified port 3128 is used (the default port for squid)
(In reply to comment #1) > I assume only string passed from RHEVM without > any validation is sent to client controller, correct? That's correct.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-0921.html