Hello Centos7.3 Proxy connection Using HTML client and code (below) to connect thru Proxy
$ cat > multifile.txt <<EOF ubuntu1|secretpassword1|1000|1000|:100 ubuntu2|secretpassword2|1000|1000|tcp:127.0.0.1:10000 EOF $ xpra start --start-child=/bin/gnome-calculator --bind-tcp=0.0.0.0:10000 :100 -d auth $ xpra proxy :13 --bind-tcp=0.0.0.0:10002 --tcp-auth=multifile:filename=multifile.txt -d auth
Tried:
and all the time "Error: password file is missing" Thank you
I believe that you're being bitten by the same issue as ticket:1264#comment:7 : you have to use absolute paths for filenames when the server daemonizes. r15488 now allows relative file paths. (please always specify what version you are running)
Relevant excerpts from the proxy's "-d auth" log output should look like this:
init_auth(..) auth class=None, tcp auth class=('multifile', <class 'xpra.server.auth.multifile_auth.Authenticator'>, {'filename': 'multifile.txt'}), ssl auth class=('multifile', <class 'xpra.server.auth.multifile_auth.Authenticator'>, {'filename': 'multifile.txt'}), vsock auth class=None Authentication required by multi password file authenticator module sending challenge for username 'ubuntu1' using hmac+sha512 digest processing authentication with multi password file, response=f919cd5..., client_salt=646261..., challenge_sent=True, digest_modes=['hmac', 'xor', 'hmac+whirlpool', 'hmac+sha512', 'hmac+sha384', 'hmac+sha256', 'hmac+sha224', 'hmac+sha1', 'hmac+sha', 'hmac+ripemd160', 'hmac+md5', 'hmac+md4', 'hmac+ecdsa-with-SHA1', 'hmac+dsaWithSHA', 'hmac+dsaEncryption', 'hmac+SHA512', 'hmac+SHA384', 'hmac+SHA256', 'hmac+SHA224', 'hmac+SHA1', 'hmac+SHA', 'hmac+RIPEMD160', 'hmac+MD5', 'hmac+MD4', 'hmac+DSA-SHA', 'hmac+DSA'] authenticate_hmac(f919cd57..., dba8c52b7...) mtime(/home/antoine/tmp/multifile.txt)=1491124949.21 loaded 94 bytes from 'multifile.txt' ... authenticate: auth-info(ubuntu1)=('secretpassword1', 1000, 1000, [':100'], {}, {}) multifile authenticate_hmac(f919cd..) password='secretpassword1', hex(salt)=0601560e560.., hash=f919cd57... authentication challenge passed
@Denis01: please close if that works for you. Please also edit the title: AFAIK, this has nothing to do with auth=allow.
(editing ticket title)
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1480