apt/methods, branch 1.2.11

allow uncompressed files to be empty in store again

2016-04-14T14:55:35Z

With the previous fix for file applied we can again hit repositories which contain uncompressed empty files, which since the introduction of the central store: method wasn't accounted for anymore as we forbid empty compressed files.

fix Alt-Filename handling of file method

2016-04-14T14:15:39Z

A silly of-by-one error in the stripping of the extension to check for the uncompressed filename broken in an attempt to support all compressions in commit a09f6eb8fc67cd2d836019f448f18580396185e5. Fixing this highlights also mistakes in the handling of the Alt-Filename in libapt which would cause apt to remove the file from the repository (if root has the needed rights – aka the disk isn't readonly or similar)

Allow lowering trust level of a hash via config

2016-03-28T12:59:33Z

Introduces APT::Hashes:: with entries Untrusted and Weak which can be set to true to cause the hash to be treated as untrusted and/or weak.

handle gpgv's weak-digests ERRSIG

2016-03-22T00:58:45Z

Our own gpgv method can declare a digest algorithm as untrusted and handles these as worthless signatures. If gpgv comes with inbuilt untrusted (which is called weak in official terminology) which it e.g. does for MD5 in recent versions we should handle it in the same way. To check this we use the most uncommon still fully trusted hash as a configureable one via a hidden config option to toggle through all of the three states a hash can be in.

properly check for "all good sigs are weak"

2016-03-21T21:47:17Z

Using erase(pos) is invalid in our case here as pos must be a valid and derefenceable iterator, which isn't the case for an end-iterator (like if we had no good signature). The problem runs deeper still through as VALIDSIG is a keyid while GOODSIG is just a longid so comparing them will always fail. Closes: 818910

Make the weak signature message less ambigious

2016-03-16T19:37:42Z

There was a complaint that, in the previous message, the key fingerprint could be mistaken for a SHA1 digest due to the (SHA1) after it. Gbp-Dch: ignore

methods/gpgv: Rewrite error handling and message

2016-03-16T16:56:50Z

This should be easy to extend in the future and allow us to simplify the error handling cases somewhat. Thanks: Ron Lee for wording suggestions

methods/gpgv: Warn about SHA1 (and RIPEMD-160)

2016-03-15T11:33:21Z

We will drop support for those in the future. Also adjust the std::array to be a std::vector, as that's easier to maintain.

apt-pkg/acquire-worker.cc: Introduce 104 Warning message

2016-03-15T11:33:21Z

This can be used by workers to send warnings to the main program. The messages will be passed to _error->Warning() by APT with the URI prepended. We are not going to make that really public now, as the interface might change a bit.

methods/gpgv: Correctly handle weak signatures with multiple keys

2016-03-15T11:33:21Z

We added weak signatures to BadSigners, meaning that a Release file signed by both a weak signature and a strong signature would be rejected; preventing people from migrating from DSA to RSA keys in a sane way. Instead of using BadSigners, treat weak signatures like expired keys: They are no good signatures, and they are worthless. Gbp-Dch: ignore