[prev in list] [next in list] [prev in thread] [next in thread]
List: kmail-devel
Subject: [Bug 84355] New: SMTP-AUTH: Interop Problem with the "PLAIN"
From: Lars Uffmann <lu-kdebugs () cachescrubber ! org>
Date: 2004-07-02 9:34:10
Message-ID: 20040702093410.29469.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=84355
Summary: SMTP-AUTH: Interop Problem with the "PLAIN" Auth-Mech
(RFC2595)
Product: kmail
Version: unspecified
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kmail-devel kde org
ReportedBy: lu-kdebugs cachescrubber org
Version: KMail 1.6.2 (using KDE KDE 3.2.3)
Installed from: I Don't Know
RFC2595 (TLS/PLAIN Auth-mech) and SASL in general use the concept of an authorization \
id vs. authentication id.
initial authentication data for PLAIN is:
> > > RFC2595
message = [authorize-id] NUL authenticate-id NUL password
The client sends the authorization identity (identity to
login as), followed by a US-ASCII NUL character, followed by the
authentication identity (identity whose password will be used),
followed by a US-ASCII NUL character, followed by the clear-text
password.
The client may leave the authorization identity empty to
indicate that it is the same as the authentication identity.
<<<
KMail (>=1.6.2) sends:
username NUL username NUL password
which seems OK when reading rfc2595.
However, some Servers behave different if the authorization identity is not NUL. So \
it might be better for interoperability to just issue
NUL username NUL password
when no proxy authorization is requested.
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic