Merge branch 'develop' into debian-develop
Redirect delgroup output to /dev/null in postrm
Improve logging / exception handling
Merge branch 'debian-feature-async-control' into debian-develop
Conflicts: debian/control debian/dirs debian/vncauthproxy.default debian/vncauthproxy.init
Merge branch 'feature-async-control' into develop
Merge branch 'feature-async-control' into debian-feature-async-control
Fix error in auth file handling
Don't crash on an empy auth file
Don't crash on an empty auth file. Also correct a typo with the `no_ssl`opt.
Add vncauthproxy user/group
Bump version to 1.4~rc2-1
Signed-off-by: Stratos Psomadakis <psomas@grnet.gr>
Add DAEMON_OPTS variable in vncauthproxy.default
Add example user auth file
Minor change to pkg descr
Add /var/lib/vncauthproxy/ to dirs
Initial Debian packaging
Drop daemon's privileges
Since there is no support for this in the daemon itself nor a properconfiguration file, do that in the (Debian) init script by using a/etc/default/vncauthproxy file plus start-stop-daemon.
Minor fixes to the Debian packaging
Update debian packaging after script name change
Update debian packaging to reflect console script name changevncauthproxy.py -> vncauthproxy in setup.py.
Update maintainer field in Synnefo branch
Add the `snf-' prefix to the package name
Install default and init.d file as `vncauthproxy'
This is done to ensure there is an upgrade path, if package`vncauthproxy' is already installed
Update debian/changelog before release
Add example users file and users file checks
Add an example users file and fail if there are no users defined in thefile.
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.
Set SO_REUSEADDR for the control socket
Fix typos/mistakes introduced by the refactoring
Code refactoring
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....
Make control connection handling async
For every incoming control connection, accept() inside the main loop anddispatch the connection handling/establishment to a new greenlet.
The async handling of the control connections ensures that vncauhtproxy won't...
Bump version to 1.4-1
Merge branch 'master' into debian-master
Merge branch 'release-1.4' into develop
Update version to 1.4
Merge branch 'release-1.4' into debian-release-1.4
Modify default port range for port pool
The default port range used for automatic port selectionwas chosen to be the ephemeral port range. This was the wrongthing to do, because it may conflict with ports used for outgoingconnections from the host on which vncauthproxy runs,...
Bump version to rc2
Update version to 1.4rc1 (release branch)
Bump version for next release
Create a docs stub to keep the CI system happy
Use single setup.py in ci/install.sh
Use devflow-update-version in ci/install.sh
« Previous 1 2 3 4 Next » (51-100/160) | Per page: 25, 50, 100
Also available in: Atom