View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000131 | apt-panopticon | Feature | public | 2019-12-23 01:38 | 2024-01-10 07:21 |
Reporter | onefang | Assigned To | onefang | ||
Priority | none | Severity | trivial | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Summary | 0000131: Release files can be dated in the future? | ||||
Description | The newer apt has a check that Release files are not too far in the future, and a config option for what "too far in the future" means, which defaults to 10 seconds. I have no clue why they would do such a thing, but someone stumbled across it when their time was set wrong. So check it I guess. | ||||
Tags | No tags attached. | ||||
DelTomix discovered how this could happen. Switching timezones. For example cloning a system that is from a different timezone, but not updating it. Confusion about what timezone the hardware clock is in, coz Micro$oft. Moving to a different timezone and not telling your computer. So the time shown on their computer looks correct, but the timezone is wrong. They may not be looking at the timezone, so wont notice. Apt notices however, and thinks the Release file is from the future. |
|