email MIME splitting
Open
Nobody has claimed this yet.
3.10
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
topic-email
type-security
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43123 |
|---|---|
| Nosy | @warsaw, @bitdancer, @rrhodes |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2021-02-04.12:48:46.668>
labels = ['type-security', '3.8', 'expert-email', '3.10', '3.7', '3.9']
title = 'email MIME splitting'
updated_at = <Date 2021-04-12.16:50:21.791>
user = 'https://bugs.python.org/martinortner'
bugs.python.org fields:
activity = <Date 2021-04-12.16:50:21.791>
actor = 'trrhodes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-02-04.12:48:46.668>
creator = 'martin.ortner'
dependencies = []
files = []
hgrepos = []
issue_num = 43123
keywords = ['patch']
message_count = 3.0
messages = ['386479', '386589', '390867']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'trrhodes', 'martin.ortner']
pr_nums = ['24475']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'security'
url = 'https://bugs.python.org/issue43123'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the migrated BPO issue 43123 and PR python/cpython#24475, then inspect the email component's current MIME-splitting behavior. The payload names no files or tests; done would require confirming the intended security fix and its regression coverage before changing the open patch-review work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100