GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||
GeezerVison is showing github.com — gh-102988: Detect email address parsing errors and return empty tuple to indicate the parsing error (old API) by tdwyer · Pull Request #105127 · python/cpython Conversation
|
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I had to create a new PR to replace the last one because Git got all messed up. This is the old PR: #102990 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Hum... it looks like CVE-2019-16056 was only fixed for getaddresses() parseaddr() |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Should I add that NEWS entry that the Bot is asking for? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
I think it is needed, NEWS entry is required for most code modifications 😄. Please see: https://devguide.python.org/core-developers/committing/#updating-news-and-what-s-new-in-python |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I added NEWS entry, and all Unit tests have passed. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Docs updated, auto-merge set. The backports beyond 3.12 will require manual work to get version numbered things right. I'd like to let this bake in 3.12beta4 & 3.12rc1 for a while first to see if any practical issues arise before landing the backports in older releases. it is a security issue so we could backport it all the way to 3.8, but lets see how things go first. it is not high severity. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @tdwyer and @gpshead, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
… tuple to indicate the parsing error (old API) (pythonGH-105127) Detect email address parsing errors and return empty tuple to indicate the parsing error (old API). This fixes or at least ameliorates CVE-2023-27043. --------- (cherry picked from commit 18dfbd0) Co-authored-by: Thomas Dwyer <[email protected]> Co-authored-by: Gregory P. Smith <[email protected]>
|
Sorry @tdwyer and @gpshead, I had trouble checking out the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-106612 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…y tuple to indicate the parsing error (old API) (GH-105127) (#106612) gh-102988: Detect email address parsing errors and return empty tuple to indicate the parsing error (old API) (GH-105127) Detect email address parsing errors and return empty tuple to indicate the parsing error (old API). This fixes or at least ameliorates CVE-2023-27043. --------- (cherry picked from commit 18dfbd0) Co-authored-by: Thomas Dwyer <[email protected]> Co-authored-by: Gregory P. Smith <[email protected]>
There was an error while loading. Please reload this page.
|
Hello @gpshead Are you going to take care of the backports/cherrypick for 3.10 and 3.11 I'd do them but I've never done that before... Hum, actually I don't think I have permission to do that. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
i'll do them, the issue remains assigned to me as a reminder. (anyone can do it, it's just a matter of creating your PR as a fork of the relevant release branch and selecting the matching base branch in the github ui at pr creation time) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Please see https://devguide.python.org/core-developers/committing/#backporting-changes-to-an-older-version for details. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
this appears to have caused #106669 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| This method returns a list of 2-tuples of the form returned by ``parseaddr()``. | ||
| *fieldvalues* is a sequence of header field values as might be returned by | ||
| :meth:`Message.get_all <email.message.Message.get_all>`. Here's a simple | ||
| example that gets all the recipients of a message:: |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
@tdwyer Is this right? Isn’t the next paragraph still a literal block? Why have you removed this colon?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…g errors and return empty tuple to indicate the parsing error (old API) (python#105127)" This reverts commit 18dfbd0. See python#106669.
… parsing errors ... (pythonGH-105127)" (pythonGH-106733) This reverts commit 18dfbd0. Adds a regression test from the issue. See python#106669.. (cherry picked from commit a31dea1) Co-authored-by: Gregory P. Smith <[email protected]>
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.