After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 308209 - SASL LOGIN mechanism protocol violation
SASL LOGIN mechanism protocol violation
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: Future
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-06-18 18:18 UTC by Greg Hudson
Modified: 2005-09-28 12:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to correct use of SASL login mechanism (346 bytes, patch)
2005-06-18 18:19 UTC, Greg Hudson 		none Details | Review

Description Greg Hudson 2005-06-18 18:18:42 UTC 
Please describe the problem:
When using the SASL LOGIN method, Evolution sends the username as an initial
response.  According to my reading of the specification (such as it is; I had to
dig for the expired draft-murchison-sasl-login I-D), this is not kosher; the
login method begins with a server challenge, not a client initial response.

Some versions of SASL server code will accept what Evolution does, but some
apparently will not.

I will attach a suggested fix.  I am unfortunately not in a position to test
this fix, but it seems trivial.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Greg Hudson 2005-06-18 18:19:53 UTC 
Created attachment 47963 [details] [review]
Patch to correct use of SASL login mechanism
Comment 2 Gautham Arumilli 2005-07-02 02:01:00 UTC 
I can confirm that this patch fixes the problem I was having with SMTP AUTH
(using LOGIN) on MIT's outgoing post server using evolution-data-server 1.2.1.
Any word on when this patch might be applied to the main tree?
Comment 3 Harish Krishnaswamy 2005-09-28 12:31:00 UTC 
Removed erroneous target milestone values and set them to FUTURE