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

Swiften 3 isn't authenticating using PLAIN (with working TLS) #60

Closed
lnjX opened this issue May 2, 2017 · 6 comments
Closed

Swiften 3 isn't authenticating using PLAIN (with working TLS) #60

lnjX opened this issue May 2, 2017 · 6 comments

Comments

@lnjX
Copy link

lnjX commented May 2, 2017

I even have allowed PLAIN without TLS.

Swift::ClientOptions options;
options.allowPLAINWithoutTLS = true;

client->connect(options);
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<stream to="chat.hipchat.com" version="1.0">
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<stream version="1.0" from="chat.hipchat.com" id="f504b137047f3a7f">
 <features>
  <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls">
   <required></required>
  </starttls>
 </features>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"></proceed>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<stream to="chat.hipchat.com" version="1.0">
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<stream version="1.0" from="chat.hipchat.com" id="3d4078fac4b2ef5c">
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<features>
 <auth xmlns="http://jabber.org/features/iq-auth"></auth>
 <auth xmlns="http://hipchat.com"></auth>
 <mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
  <mechanism>PLAIN</mechanism>
  <mechanism>X-HIPCHAT-OAUTH2</mechanism>
 </mechanisms>
 <authrestartlogic xmlns="http://hipchat.com"></authrestartlogic>
 <compression xmlns="http://jabber.org/features/compress">
  <method>zlib</method>
 </compression>
</features>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<compress xmlns="http://jabber.org/protocol/compress">
 <method>zlib</method>
</compress>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<compressed xmlns="http://jabber.org/protocol/compress"></compressed>

(after two exactly the same retrys of this, the connection just fails)

One of the problems here is probably that HipChat uses it's own XMPP extensions.


FYI: With gajim it's just working fine.

@vitalyster
Copy link
Contributor

vitalyster commented May 3, 2017

What if you will disable stream compression ?

@lnjX
Copy link
Author

lnjX commented May 3, 2017

I'll try that today. Thanks.

@lnjX
Copy link
Author

lnjX commented May 3, 2017

Yeah it works without compression! But shouldn't Swift/Swiften automatically recognize if stream compression works or works not?

@tfar tfar closed this as completed May 3, 2017
@tfar tfar reopened this May 3, 2017
@tfar
Copy link
Collaborator

tfar commented May 3, 2017

Sorry. Pressed the wrong button.

@Kev
Copy link
Member

Kev commented May 5, 2017

I think this is going to be hard to diagnose without help from the server vendor unless you can MITM the TLS negotiation so we can get a wireshark of the compression setup.

@Kev
Copy link
Member

Kev commented Feb 28, 2018

This issue seems to have gone dead, and looks like a server compression bug. Closing until/unless we get more information to debug with.

@Kev Kev closed this as completed Feb 28, 2018
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