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

memory corruption sasl reconnect? #1055

ailin-nemui opened this issue Jun 12, 2019 · 1 comment


None yet
1 participant
Copy link

commented Jun 12, 2019


reported by @ilbelkyr

I just accidentally reproduced the SASL failure on autoreconnect issue, and again, doing /rmreconns and connecting manually fixed it. I managed to grab rawlog, and apparently it's sending different things in the AUTHENTICATE message; I'll see if I can share them without revealing passwords

fwiw, what it's sending in the failure case is valid base64; but instead of ilbelkyr\0ilbelkyr\0password, it puts ilbelkyr (my username) as the password, and some random base64-looking data (which doesn't appear to decode to anything meaningful) as the username


This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2019

missing strdup?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.