Some revision_dates are created in the future
Bug #340860 reported by
Tim Penhey
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Tim Penhey | ||
Bug Description
Through either local clock drift, plain wrong localtime, or malicious intent, it is possible that the revisiondate stored on the revision is a future time.
We should cap the revision_date recorded in the database to be the date_created value.
| Changed in launchpad-bazaar: | |
| assignee: | nobody → thumper |
| importance: | Undecided → High |
| milestone: | none → 2.2.3 |
| status: | New → In Progress |
| Changed in launchpad-bazaar: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in launchpad-bazaar: | |
| status: | Fix Committed → Triaged |
| Changed in launchpad-bazaar: | |
| status: | Triaged → In Progress |
Revision history for this message
| Stuart Bishop (stub) wrote | #2 |
| Changed in launchpad-bazaar: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad-bazaar: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Liar, liar, pants on fire.