Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to generate challenge response: strings must be equal length #323

Open
sbradnick opened this issue Oct 11, 2024 · 3 comments
Open

Comments

@sbradnick
Copy link

After changes between 0aa7703 and ed0b9fc I can't successfully connect to an xpra session via https. I'm prompted for the user password, but then dropped back to a login screen which shows the following message:

You were disconnected for the following reason:

failed to generate challenge response: strings must be equal length

Reinstalling [an rpm based off] 0aa7703 makes it work again.

Using openSUSE-Tumbleweed on both client/server and my startup command is:

xpra start --start=xterm \
  --bind-tcp=<my_ip>:10000 \
  --tcp-auth=sys \
  --ssl-cert=/etc/xpra/ssl-cert.pem \
  --ssl-key=/etc/xpra/ssl-cert.key \
  --ssl=on
@totaam
Copy link
Collaborator

totaam commented Oct 11, 2024

The changes from #314 are disruptive, which is why I will be releasing xpra 6.2 soon to go with it.
I believe that the current release of xpra-html5 (16.2 at time of writing) should still work with any recent version of xpra - does it not?

@sbradnick
Copy link
Author

The changes from #314 are disruptive, which is why I will be releasing xpra 6.2 soon to go with it.

Gotcha. I can see it being an incompatibility between ed0b9fc & Xpra-org/xpra@57777eda (which are the ones I'm using). I realize 0aa7703 isn't part of a release at this point - apologies if this issue is a bit pre-emptive.

All is good between 0aa7703 and Xpra-org/xpra@57777eda

I can double-check again later when changes in Xpra-org/xpra hit to support what #314 does 👍

@totaam
Copy link
Collaborator

totaam commented Oct 12, 2024

apologies if this issue is a bit pre-emptive.

Not at all, this is good to know and needs fixing.
I'm just ultra paranoid about breaking the stable repo releases, so I panicked a bit!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants