-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
bpo-45706: Add imaplib.IMAP4.login_plain #29398
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -330,8 +330,22 @@ An :class:`IMAP4` instance has the following methods: | |
.. method:: IMAP4.login_cram_md5(user, password) | ||
|
||
Force use of ``CRAM-MD5`` authentication when identifying the client to protect | ||
the password. Will only work if the server ``CAPABILITY`` response includes the | ||
phrase ``AUTH=CRAM-MD5``. | ||
the password. It will only work if the server ``CAPABILITY`` response includes | ||
the phrase ``AUTH=CRAM-MD5``. | ||
|
||
|
||
.. method:: IMAP4.login_plain(login, password) | ||
|
||
Authenticate using PLAIN SASL mechanism. | ||
|
||
This is a plain-text authentication mechanism that can be used | ||
instead of :meth:`IMAP4.login()` when UTF-8 support is required. | ||
See :RFC:`6855`, page 5. | ||
|
||
It will only work if the server ``CAPABILITY`` response includes | ||
the phrase ``AUTH=PLAIN``. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The module partially supports RFC 3501, which says that AUTH=PLAIN is mandatory. I understand that means advertising it in CAPABILITY is optional, so it might work regardless. |
||
|
||
.. versionadded:: 3.11 | ||
|
||
|
||
.. method:: IMAP4.logout() | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -614,6 +614,18 @@ def login(self, user, password): | |
return typ, dat | ||
|
||
|
||
def login_plain(self, user, password): | ||
"""Authenticate using PLAIN SASL mechanism. | ||
|
||
This is a plain-text authentication mechanism that can be used | ||
instead of login() when UTF-8 support is required. | ||
""" | ||
return self.authenticate( | ||
"PLAIN", | ||
lambda _: "{0}\x00{0}\x00{1}".format(user, password).encode() | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This sets the authorization identity (authzid) to the user name. Wouldn’t it be better to allow omitting authzid by default, let the server derive it? https://datatracker.ietf.org/doc/html/rfc4616#section-2 f'\x00{user}\x00{password}'.encode('utf-8') |
||
) | ||
|
||
|
||
def login_cram_md5(self, user, password): | ||
""" Force use of CRAM-MD5 authentication. | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Add :meth:`imaplib.IMAP4.login_plain`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure that referring to RFC 6855 is that relevant. All it does is recommend against UTF-8 support with LOGIN, and say that AUTHENTICATE supports UTF-8.