History | View | Annotate | Download (6.3 kB)
Add support for control connection authentication
Since vncauthproxy no longer uses Unix domain sockets for the controlconnection handling, authentication handling, which was done with POSIXfile permissions, must be implemented in vncauthproxy.
The /var/lib/vncauthproxy/users file (configurable) acts as an...
Use SSL/TLS for control connections
Control connections now use SSL/TLS by default. Since, vncauthproxy controlconnections now use TCP/IP instead of Unix domain sockets, sensitiveinformation could be sent over possibly untrusted / insecure channels.
Minor lexical fixes
Use TCP instead of UNIX sockets (first try)
Initial 'implementation' of vncauthproxy using TCP sockets instead ofUNIX domain sockets for control connections.
By default, it will bind to 127.0.0.1:24999 (forwarding ports start atTCP 25000). The client was changed accordingly....
Support argument parsing in command line client
Make the vncauthproxy client a proper command line tool,by adding support for argument parsing. Also output debugginginformation to stderr.
Make source PEP8-compliant
Major restructuring of the directory layout
Create a proper Python package called "vncauthproxy" and move the proxyand the client there; also create a vncauthproxy.py, that imports fromthe package and calls its main()