diff options
author | Christophe Fergeau <cfergeau@redhat.com> | 2012-03-20 14:51:07 +0100 |
---|---|---|
committer | Christophe Fergeau <cfergeau@redhat.com> | 2012-03-20 16:53:40 +0100 |
commit | 3d452a312be3ae1691e9ae310ca15072b04f67c9 (patch) | |
tree | 8b8526efe12321cfdc28dcab6129ad916466dfa8 /python_modules | |
parent | 01c6f4d2c60ecc360353049f757c60a7fffc81a6 (diff) | |
download | spice-3d452a312be3ae1691e9ae310ca15072b04f67c9.tar.gz spice-3d452a312be3ae1691e9ae310ca15072b04f67c9.tar.xz spice-3d452a312be3ae1691e9ae310ca15072b04f67c9.zip |
Don't limit spice controller socket name to 50 chars
The spice controller socket name used to be hardcoded to
/tmp/SpiceController-%lu.uds and generated using snprintf. A 50 bytes
buffer was enough for that, but this was changed in commit 79fffbf95
because this was predictable and allowed other users on the system
to sniff the browser/client communication. spicec now uses the value
of the environment SPICE_XPI_SOCKET as the name of the socket to use.
However, since the name that is used is no longer generated by spicec,
no assumption can be made about its size. Currently, the socket is
created inside the user home directory, which means that if the
user name is too long, spicec will not be able to read the controller
socket name.
This commit directly uses the string from getenv as he name of the
controller socket (on Linux) instead of limiting its size to 50 characters,
which should fix this issue.
This fixes rhbz #804561
Diffstat (limited to 'python_modules')
0 files changed, 0 insertions, 0 deletions