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)
P.S. I would expect that setting XPRA_PASSWORD
is enough, according to the documentation.
Thanks for reporting this. Fixed in r12452.
Tested with:
XPRA_PASSWORD=hello1234 xpra start :100 --bind-tcp=0.0.0.0:10000 --start-child="xterm" \ --tcp-auth=env --tcp-encryption=AES
client:
echo -n hello1234 > pass.txt xpra attach tcp:192.168.0.1:10000 \ --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)
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
?
No, server. The client does not use any auth modules.
Not heard back, assuming this is fixed.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1179