Asks for password even when GSSAPI is selected

Bug #95966 reported by Jelmer Vernooij
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
claws-mail (Fedora)
Fix Released
Medium
claws-mail (Ubuntu)
Fix Released
Undecided
Unassigned
sylpheed-claws-gtk2 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

  affects /ubuntu/sylpheed-claws-gtk2

When I have selected GSSAPI as SASL authentication mechanism in
sylpheed it will ask me for a password (even though I have a valid
Kerberos ticket). After entering a random string, it is able to
continue to the server successfully.

--
Jelmer Vernooij <email address hidden> / Jabber: <email address hidden>
http://samba.org/~jelmer/

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha/beta?

Changed in sylpheed-claws-gtk2:
status: New → Incomplete
Revision history for this message
Scott Kitterman (kitterman) wrote :

Package was renamed, so for Intrepid claws-mail is what should be checked.

Revision history for this message
In , Jon (jon-redhat-bugs) wrote :

Description of problem:
When using GSSAPI authentication with Kerberos, a password dialog is still displayed. claws will not continue fetching mail until something is entered. Note that an actual password is not required. A random character or two is all that is needed to dismiss the dialog and have Claws use gssapi to authenticate.

Version-Release number of selected component (if applicable):
claws-mail-3.7.0-1.fc10.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Set Authentication Method to GSSAPI for a mail server that supports it.
2. kinit
3. Click on Inbox or Get Mail

Actual results:
The password dialog box appears, and refuses to authenticate until a random string is entered.

Expected results:
No password dialog, Claws goes ahead with GSSAPI authentication uninterrupted.

Additional info:

Revision history for this message
In , Colin (colin-redhat-bugs) wrote :

Created attachment 337072
Patch that should fix it

We fixed it once, but reverted the patch because of testing and it was too near a release. We since forgot to reapply it.

Could you test the attached patch (which should apply fine) and tell me whether it works fine?

I wouldn't want to apply it without testing.

Thanks in advance!

Revision history for this message
Colin Leroy-Mira (colin-colino) wrote :

Can you test the patch at https://bugzilla.redhat.com/show_bug.cgi?id=486422 ?

Thanks!

Revision history for this message
In , Jon (jon-redhat-bugs) wrote :

Yes, this patch works just fine.

Thanks!

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

closing for the old package as won't fix

Changed in sylpheed-claws-gtk2 (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
In , Jeff (jeff-redhat-bugs) wrote :

Moving this back to ASSIGNED. The patch doesn't seem to be in yet (at least not in rawhide). Any idea when this will make it into a release? Below is a snippet of the network log:

----------------[snip]----------------
[07:45:21] IMAP4< * OK IMAP4 ready
* IMAP connection is un-authenticated <<<< (password dialog pops up here)
[07:45:27] IMAP4> 1 CAPABILITY
[07:45:27] IMAP4< * CAPABILITY ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ID IDLE IMAP4rev1 LIST-EXTENDED LITERAL+ MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=ektx SASL-IR SEARCHRES UIDPLUS UNSELECT WITHIN AUTH=PLAIN AUTH=GSSAPI
[07:45:27] IMAP4< 1 OK completed
[07:45:27] IMAP4> Logging jlayton to mail.foo.bar using GSSAPI
[07:45:27] IMAP4< completed
** IMAP error on mail.foo.bar: LOGIN error
[07:45:27] IMAP4< Error logging in to mail.foo.bar
[07:45:34] IMAP4< * BYE Zimbra IMAP server terminating connection
[07:45:34] IMAP4< 2 OK completed
----------------[snip]----------------

I'm also having problems authenticating at all with GSSAPI, but that seems to be a separate issue.

Changed in claws-mail (Fedora):
status: Unknown → In Progress
Revision history for this message
In , Andreas (andreas-redhat-bugs) wrote :

Will take care of it asap.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

claws-mail-3.7.1-2.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/claws-mail-3.7.1-2.fc10

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

claws-mail-3.7.1-2.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/claws-mail-3.7.1-2.fc11

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

claws-mail-3.7.1-2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with
 su -c 'yum --enablerepo=updates-testing update claws-mail'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-6722

Changed in claws-mail (Fedora):
status: In Progress → Fix Committed
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

claws-mail-3.7.1-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

claws-mail-3.7.1-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.

Changed in claws-mail (Fedora):
status: Fix Committed → Fix Released
Revision history for this message
In , Jon (jon-redhat-bugs) wrote :

Verified on F10 x86_64

Revision history for this message
Ilya Barygin (randomaction) wrote :

This is fixed in 3.7.2.

Changed in claws-mail (Ubuntu):
status: New → Fix Released
Changed in claws-mail (Fedora):
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.