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

digest-md5 mechanism doesn't work #4

Open
edwintorok opened this issue May 17, 2015 · 4 comments
Open

digest-md5 mechanism doesn't work #4

edwintorok opened this issue May 17, 2015 · 4 comments

Comments

@edwintorok
Copy link

I get 'not authorized' when trying to connect to openfire, and out.txt in jackline says it tried to use DIGEST-MD5.

For now I worked this around by disabling DIGEST-MD5 completely (the connection is secured using STARTTLS, so PLAIN is fine for me):

-      if List.mem "DIGEST-MD5" m then
-        sasl_digest session_data password nextstep
-      else if List.mem "PLAIN" m then
+      if List.mem "PLAIN" m then

Please provide a way to configure what SASL mechanisms to use, and let me know if I can provide any info on debugging why DIGEST-MD5 doesn't work.

@hannesm
Copy link

hannesm commented May 18, 2015

could you paste the SASL-parts from the log? for me, digest-md5 works...

@Neustradamus
Copy link

Please note that DIGEST-MD5 is not secure, it must be SCRAM-SHA-X(-PLUS)...

@ermine
Copy link
Owner

ermine commented Sep 29, 2020 via email

@edwintorok
Copy link
Author

Well I wasn't trying to use digest-md5, I was trying to avoid using it (the server was offering it and the client was choosing that over plain, and failed to work). The problematic openfire installation doesn't exist anymore so unfortunately I can't provide logs to debug why digest-md5 doesn't work.

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

4 participants