Adium

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#8803 closed defect (fixed)

No password prompt when one is not stored with the account results in connection error

Reported by: dgc Owned by: nobody
Milestone: Adium 1.2.1 Component: Service/XMPP (Jabber)
Version: Severity: regression
Keywords: xmpp jabber Cc:
Patch Status:

Description

There appears to be a regression in XMPP handling. I have an account set from 1.1.4 and earlier, connecting to a Wildfire server at im.uchicago.edu:5223 using "Force old-style SSL" and "Strict certificate checks" options. When Adium 1.2 tries to connect, it quickly gets "Error: Read Error". Nothing appears in Console.app.

This account worked as above in 1.1.4 and earlier, and only stopped as soon as I upgraded to 1.2. When I remove my Application Support/Adium 2.0 folder and define the account from scratch, I still have the error. And iChat can connect and communicate from the same computer, so the server is not blocking me in any way. According to the server admins nothing has been changed server-end.

Change History (14)

comment:1 Changed 13 years ago by dgc

Additional datum: I do not have a stored password (I enter it upon login). If I store the password, Adium connects and goes online. If I remove the stored password and disconnect, I again get a read error.

comment:2 Changed 13 years ago by Jordan

Milestone: Adium X 1.2.1
Severity: normalregression

Does it request the password, then give a read error? Or only throw a read error and no request for the password even though you haven't supplied it?

comment:3 Changed 13 years ago by dgc

The latter, exactly. In the Preferences/Accounts pane, I see connecting.... followed by the "Error: Read Error" (openssl getting a disconnect, perhaps?) message and then a retry delay. No dialog ever comes up for the password.

comment:4 Changed 13 years ago by Jorj Bauer

Same thing here (different, but still Openfire, server). I have one report that someone with 10.4 can use Adium 1.2 properly, but my machine (10.5) does this same thing.

Also happens with port 5222 and not "force old-style", with and without "do strict certificate checks".

comment:5 Changed 13 years ago by Jorj Bauer

This broke between 1.2b4 and 1.2b6. (1.2b5 just crashes.) It appears that Tiger (10.4) users are okay, and Leopard (10.5) users can't use anything beyond 1.2b4.

comment:6 Changed 13 years ago by Jorj Bauer

Is this the same bug as 8787, or something different?

comment:7 Changed 13 years ago by dgc

I don't believe it's the same as 8787:

  • 8787 states that iChat has the same issue, but I don't have this problem with iChat
  • I don't see any messages about invalid certificates anywhere
  • it works if I store the password in Adium; it fails only when I want Adium to prompt me (and it doesn't)

It feels like it's confined to the Jabber component's interaction with the UI -- it's simply not asking for a password. But I know it *could* be more complicated than that.

comment:8 Changed 13 years ago by Jordan

Summary: xmpp with ssl may be borkenNo password prompt when one is not stored with the account results in connection error

comment:9 Changed 13 years ago by Jorj Bauer

Yes, that's it exactly - if the password isn't stored, it doesn't work. The 10.4 vs 10.5 is probably a red herring; it's just different user behavior.

comment:10 Changed 13 years ago by dgc

OK, cool. Sorry the initial report was so far off. I hadn't thought to try with a stored password when I filed it, and I can't try without SSL, so I just listed the known conditions. :)

comment:11 Changed 13 years ago by Evan Schoenberg

Resolution: fixed
Status: newclosed

(In [22261]) Work around a bug in old openfire servers if no password is sent in which they send 'read error' instead of and invalid password error code. Fixes #8803

comment:12 Changed 13 years ago by Evan Schoenberg

(In [22262]) merged [22261]: Work around a bug in old openfire servers if no password is sent in which they send 'read error' instead of and invalid password error code. Fixes #8803

comment:13 Changed 13 years ago by Evan Schoenberg

Milestone: Adium X 1.2.1Adium X 1.2.2

comment:14 Changed 13 years ago by Evan Schoenberg

Milestone: Adium X 1.2.2Adium X 1.2.1
Note: See TracTickets for help on using tickets.