#1179 closed defect (worksforme)
XPRA_ENCRYPTION_KEY fallback to XPRA_PASSWORD does not work
Reported by: | urzds | Owned by: | urzds |
---|---|---|---|
Priority: | major | Milestone: | 0.17 |
Component: | server | Version: | trunk |
Keywords: | Cc: |
Description
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)
Change History (6)
comment:1 Changed 5 years ago by
comment:2 Changed 5 years ago by
Owner: | changed from Antoine Martin to urzds |
---|
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)
comment:3 Changed 5 years ago by
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
?
comment:5 Changed 4 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Not heard back, assuming this is fixed.
comment:6 Changed 4 days ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1179
Note: See
TracTickets for help on using
tickets.
P.S. I would expect that setting
XPRA_PASSWORD
is enough, according to the documentation.