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

Prosody authentication: "Unable to interpret data from auth process, [xx bytes]" #21

Closed
MarcelWaldvogel opened this Issue Jun 20, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@MarcelWaldvogel
Contributor

MarcelWaldvogel commented Jun 20, 2017

This was experienced by @Carpintonto on Ubuntu 16.04.2 LTS:

Prosody log /var/log/prosody/prosody.log shows messages akin to:

example.com:auth_external warn Unable to interpret data from auth process, [41 bytes]
@MarcelWaldvogel

This comment has been minimized.

Show comment
Hide comment
@MarcelWaldvogel

MarcelWaldvogel Jun 21, 2017

Contributor

Playing around with mod_auth_external.lua (printing those bytes), it seems to be a verbatim echo of the auth request sent to external_cloud.py. Why this is happening, is currently beyond me, as mod_auth_external.lua sets no_local_echo = true and also the python end sees echo turned off.

(Note that mod_auth_external.lua uses a TTY/PTY pair to start the authentication process, which is unnecessary in this case (and most other cases I can currently think of).

Contributor

MarcelWaldvogel commented Jun 21, 2017

Playing around with mod_auth_external.lua (printing those bytes), it seems to be a verbatim echo of the auth request sent to external_cloud.py. Why this is happening, is currently beyond me, as mod_auth_external.lua sets no_local_echo = true and also the python end sees echo turned off.

(Note that mod_auth_external.lua uses a TTY/PTY pair to start the authentication process, which is unnecessary in this case (and most other cases I can currently think of).

@MarcelWaldvogel

This comment has been minimized.

Show comment
Hide comment
@MarcelWaldvogel

MarcelWaldvogel Jun 21, 2017

Contributor

Prosody issue 855 discusses this problem. The patch fixes it, for non-blocking access (this shouldn't bother you, unless you are using Prosody-trunk).

Contributor

MarcelWaldvogel commented Jun 21, 2017

Prosody issue 855 discusses this problem. The patch fixes it, for non-blocking access (this shouldn't bother you, unless you are using Prosody-trunk).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment