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

Password preventing connection #91

Closed
ultr41337h4xor opened this issue Feb 5, 2024 · 6 comments
Closed

Password preventing connection #91

ultr41337h4xor opened this issue Feb 5, 2024 · 6 comments
Assignees
Labels
already resolved - awaiting release Already resolved in source code, however the release containing the fix is still not out bug Something isn't working

Comments

@ultr41337h4xor
Copy link

ultr41337h4xor commented Feb 5, 2024

Hello,
very nice idea for an app, thank you for your work!

The problem I'm having is, when I type in all the info for my server and click connect the status says "Disconnected" and when I check the server log it says the client was dropped, with the reason given being "Wrong password supplied". I tried typing it by hand and copy and pasting it, however neither method works (tried copy and pasting the password when typed on a computer as well). I'm fairly certain the password is not being typed incorrectly, as it is a simple, all lowercase string of 13 alphabetical characters.

@yuroyami
Copy link
Owner

yuroyami commented Feb 6, 2024

Hi @ultr41337h4xor, much appreciated for the feedback :)

I am guessing you are hosting your own private server on a PC or trying to access one that is hosted by someone else ? Syncplay has its own set of public servers which are not password-protected. Just to clarify any misconceptions, the password feature is mainly for the server itself and not for the rooms. Provided that you're aware of all of this, the password feature may be broken (I haven't really tested it at all), could you please test using the official Syncplay PC client ?

@ultr41337h4xor
Copy link
Author

Hi @ultr41337h4xor, much appreciated for the feedback :)

I am guessing you are hosting your own private server on a PC or trying to access one that is hosted by someone else ? Syncplay has its own set of public servers which are not password-protected. Just to clarify any misconceptions, the password feature is mainly for the server itself and not for the rooms. Provided that you're aware of all of this, the password feature may be broken (I haven't really tested it at all), could you please test using the official Syncplay PC client ?

Thanks for the quick reply! It is a private, password-protected server, hosted on another one of my computers. The rooms are not password protected. The PC clients can connect without issue. I'm pretty sure the feature is broken, as I've tried connecting with version 0.12 and the mobile client connected instantly to the same server.

Maybe the problem is connected with the new TLS feature? As I tried to shut it off and couldn't turn the setting off (it resets to "on", as soon as I back out of the menu),

@yuroyami yuroyami self-assigned this Feb 6, 2024
@yuroyami yuroyami added the bug Something isn't working label Feb 6, 2024
@yuroyami
Copy link
Owner

yuroyami commented Feb 6, 2024

@ultr41337h4xor Thank you for bringing this to light. It might well be due to the TLS feature, or just a regression due to the full re-write of the code after embracing Kotlin/Native Compose multiplatform. For now, you can use an older version (such as 0.12.0), they are all mainly written for Android and do not have the TLS feature.

@Et0h
Copy link

Et0h commented Jun 20, 2024

Hard to assess what might be going wrong without an example of a password and associated hash generated from Syncplay mobile, but please bear in mind that Syncplay PC client uses hashlib.md5(config['password'].encode('utf-8')).hexdigest(). The hash is lowercase, so for example foobar becomes 3858f62230ac3c915f300c664312c63f.

@yuroyami
Copy link
Owner

@Et0h Spot on! Server was responding with {"Error": {"message": "Wrong password supplied"}} which pointed to a problem in hash. Turns out it was generated in upper case whereas it was expected in lowercase. Thanks!

@yuroyami yuroyami added the already resolved - awaiting release Already resolved in source code, however the release containing the fix is still not out label Jul 23, 2024
@yuroyami
Copy link
Owner

0.15.0 is released shipping a fix for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
already resolved - awaiting release Already resolved in source code, however the release containing the fix is still not out bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants