CVE-2008-1447 fix regression loses socket errors
Bug #252236 reported by
Scott Kitterman
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-dns (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| Dapper |
Fix Released
|
Medium
|
Scott Kitterman | ||
| Feisty |
Fix Released
|
Medium
|
Scott Kitterman | ||
| Gutsy |
Fix Released
|
Medium
|
Scott Kitterman | ||
| Hardy |
Fix Released
|
Medium
|
Scott Kitterman | ||
Bug Description
affects ubuntu/python-dns
status triaged
importance medium
subscribe ubuntu-security
My patch for python-dns failed to propagate errors on up if they were'n't
socket in use errors. Fix attached for Dapper/
already fixed. Sorry.
Scott K
| Changed in python-dns: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| status: | Triaged → Fix Released |
Revision history for this message
| Scott Kitterman (kitterman) wrote | #1 |
| Changed in python-dns: | |
| assignee: | nobody → kitterman |
| status: | Triaged → In Progress |
| assignee: | nobody → kitterman |
| status: | Triaged → In Progress |
| assignee: | nobody → kitterman |
| status: | Triaged → In Progress |
| assignee: | nobody → kitterman |
| status: | Triaged → In Progress |
Revision history for this message
| Scott Kitterman (kitterman) wrote | #2 |
Revision history for this message
| Scott Kitterman (kitterman) wrote | #3 |
Revision history for this message
| Scott Kitterman (kitterman) wrote | #4 |
Revision history for this message
| Scott Kitterman (kitterman) wrote | #5 |
| Changed in python-dns: | |
| status: | In Progress → Fix Released |
| status: | In Progress → Fix Released |
| status: | In Progress → Fix Released |
| status: | In Progress → Fix Released |
To post a comment you must log in.
In each case, these are not strictly a minimal change set to deal with regression, but I recommend this approach anyway. Sorting out the strict minimum set would take significantly more time that I don't have. I used DNS/Base.py and updated each release with the current upstream version.
1. For Hardy the only extra changes are some minimal import rearranging that upstream did in 2.3.2. This is very low risk as it will either work or fail right away. No real risk of latent defects.
2. For dapper/feisty/gutsy there are additional bug fixes that were added in later releases. These are all well tested and safe. None of them were link to changes in other files.
I have the Hardy version now running on one of my mail servers without issue.