Revision d5426b9b
| ID | d5426b9bfeca620f1b6ccd498108f71a5e54f311 |
Suggest running vncauthproxy as nobody:www-data
Running vncauthproxy as nobody:www-data makes more sense. We have better
privilege separation between apache2/gunicorn and vncauthproxy, while
gunicorn can still to connect to the vncauthproxy's control socket.
When/if vncauthproxy starts using TCP ctrl sockets instead of UNIX, this
could be omitted entirely.
We could also consider adding a separate user/group for vncauhtproxy.
Files
- added
- modified
- copied
- renamed
- deleted