Xpra: Ticket #1160: per socket authentication and encryption configuration

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 \

for encryption as well:

xpra start \

Tue, 13 Sep 2016 11:47:07 GMT - Antoine Martin: status, milestone changed

Wed, 28 Mar 2018 06:09:55 GMT - Antoine Martin: milestone changed

Tue, 05 Mar 2019 02:02:28 GMT - Antoine Martin:

See also ticket:2125#comment:4

Wed, 20 Mar 2019 05:06:15 GMT - Antoine Martin: milestone changed

Milestone renamed

Fri, 13 Sep 2019 15:45:12 GMT - Antoine Martin: priority changed

Blocker for #2125.

Mon, 23 Sep 2019 07:22:36 GMT - Antoine Martin: attachment set

work in progress patch

Mon, 23 Sep 2019 13:33:27 GMT - 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.

Tue, 15 Oct 2019 16:01:45 GMT - Antoine Martin:

r24142 fixes named pipes.

Mon, 10 Feb 2020 05:37:07 GMT - Antoine Martin: status changed; resolution set

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


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

Port 10000 uses encryption, and port 10001 does not.

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

Tue, 02 Jun 2020 03:58:43 GMT - Antoine Martin:

For client connection strings, see #2794.

Sat, 23 Jan 2021 05:16:37 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1160