per socket authentication and encryption configuration

[Antoine Martin]

Split from #1159.
We should extend the socket configuration syntax to be able to configure authentication and encryption for each socket.
This would get rid of a number of command line arguments (which we would keep temporarily for backwards compatibility, probably also still used by the client command line).

ie: for just authentication (replacing the tcp-auth command line option):

xpra start \
    --bind-tcp=0.0.0.0:10000,auth=file:filename=password.txt

for encryption as well:

xpra start \
    --bind-tcp=0.0.0.0:10000,encryption=AES:keyfile=key.txt,auth=file:filename=password.txt

[Antoine Martin]

See also ticket:2125#comment:4

[Antoine Martin]

Milestone renamed

[Antoine Martin]

Blocker for #2125.

[Antoine Martin]

work in progress patch

[Antoine Martin]

Done for authentication in r23895.
As a side-effect, we no longer initialize the authentication modules using the config object.

New related ticket: #2424.

[Antoine Martin]

r24142 fixes named pipes.

[Antoine Martin]

Per socket encryption options done in r25202 + r25203, fixup in r25209.

ie:

xpra start --start=xterm --bind-tcp=0.0.0.0:10000,encryption=AES,encryption-keyfile=./key.txt --bind-tcp=0.0.0.0:10001 -d crypto

Port 10000 uses encryption, and port 10001 does not.

See also #2460 (ssl) and #2583 (ssh).

[Antoine Martin]

For client connection strings, see #2794.