Xpra: Ticket #1179: XPRA_ENCRYPTION_KEY fallback to XPRA_PASSWORD does not work

https://www.xpra.org/trac/wiki/Encryption says:

Starting with version 0.11, one can specify the encryption key to use with the "`--encryption-keyfile=FILENAME`" command line option or fallback to the password from the authentication module in use.

However, Xpra complains, when XPRA_ENCRYPTION_KEY is not set:

xpra initialization error:
 encryption AES cannot be used without a keyfile (see --encryption-keyfile option)

Wed, 20 Apr 2016 16:27:06 GMT - urzds:

P.S. I would expect that setting XPRA_PASSWORD is enough, according to the documentation.

Thu, 21 Apr 2016 13:31:11 GMT - Antoine Martin: owner changed

Thanks for reporting this. Fixed in r12452.

Tested with:

XPRA_PASSWORD=hello1234 xpra start :100 --bind-tcp= --start-child="xterm" \
    --tcp-auth=env --tcp-encryption=AES


echo -n hello1234 > pass.txt
xpra attach tcp: \
    --encryption-keyfile=./pass.txt --password-file=./pass.txt

Does this work for you? (note: the env var will only be used if you use the env auth module)

Thu, 21 Apr 2016 13:48:31 GMT - urzds:

the env var will only be used if you use the env auth module

i.e. on the client I also have to specify --auth=env?

Thu, 21 Apr 2016 13:49:34 GMT - Antoine Martin:

No, server. The client does not use any auth modules.

Tue, 09 Aug 2016 15:05:27 GMT - Antoine Martin: status changed; resolution set

Not heard back, assuming this is fixed.

Sat, 23 Jan 2021 05:17:07 GMT - migration script:

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