per socket authentication and encryption configuration

[totaam]

Issue migrated from trac ticket # 1160

component: server | priority: critical | resolution: fixed

2016-04-08 08:44:09: antoine created the issue

---

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

[totaam]

2016-09-13 12:47:08: antoine changed status from new to assigned

[totaam]

2019-03-05 02:02:29: antoine commented

---

See also #2125#comment:4

[totaam]

2019-03-20 05:06:15: antoine commented

---

Milestone renamed

[totaam]

2019-09-13 16:45:13: antoine changed priority from major to critical

[totaam]

2019-09-13 16:45:13: antoine commented

---

Blocker for #2125.

[totaam]

2019-09-23 08:22:36: antoine uploaded file per-socket-auth.patch (39.6 KiB)

work in progress patch

[totaam]

2019-09-23 14:33:28: antoine commented

---

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

New related ticket: #2424.

[totaam]

2019-10-15 17:01:46: antoine commented

---

r24142 fixes named pipes.

[totaam]

2020-02-10 05:37:08: antoine changed status from assigned to closed

[totaam]

2020-02-10 05:37:08: antoine set resolution to fixed

[totaam]

2020-02-10 05:37:08: antoine commented

---

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).

[totaam]

2020-06-02 04:58:43: antoine commented

---

For client connection strings, see #2794.