xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Opened 6 years ago

Closed 5 years ago

Last modified 9 months ago

#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:


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 6 years ago by urzds

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

comment:2 Changed 6 years ago by Antoine Martin

Owner: changed from Antoine Martin to urzds

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)

comment:3 Changed 6 years ago by 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?

comment:4 Changed 6 years ago by Antoine Martin

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

comment:5 Changed 5 years ago by Antoine Martin

Resolution: worksforme
Status: newclosed

Not heard back, assuming this is fixed.

comment:6 Changed 9 months ago by migration script

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

Note: See TracTickets for help on using tickets.