Age | Commit message (Collapse) | Author | |
---|---|---|---|
2016-06-22 | handle weak-security repositories as unauthenticated | David Kalnischkies | |
APT can be forced to deal with repositories which have no security features whatsoever, so just giving up on repositories which "just" fail our current criteria of good security features is the wrong incentive. Of course, repositories are better of fixing their setup to provide the minimum of security features, but sometimes this isn't possible: Historic repositories for example which do not change (anymore). That also fixes problem with repositories which are marked as trusted, but are providing only weak security features which would fail the parsing of the Release file. Closes: 827364 | |||
2016-03-25 | drop confusing comma from no strong hash message | David Kalnischkies | |
2016-03-16 | Report non-transient errors as errors, not as warnings | Julian Andres Klode | |
This makes it easier to understand what really is an error and what not. | |||
2015-12-14 | show a more descriptive error for weak Release files | David Kalnischkies | |
If we can't work with the hashes we parsed from the Release file we display now an error message if the Release file includes only weak hashes instead of downloading the indexes and failing to verify them with "Hash Sum mismatch" even through the hashes didn't mismatch (they were just weak). If for some (unlikely) reason we have got weak hashes only for individual targets we will show a warning to this effect (again, befor downloading and failing the index itself). Closes: 806459 |