From 89901946f936446f439b95f1a9a85ac942ac2c92 Mon Sep 17 00:00:00 2001 From: David Kalnischkies Date: Fri, 29 Apr 2016 16:48:16 +0200 Subject: support Signed-By in Release files as a sort of HPKP Users have the option since apt >= 1.1 to enforce that a Release file is signed with specific key(s) either via keyring filename or fingerprints. This commit adds an entry with the same name and value (except that it doesn't accept filenames for obvious reasons) to the Release file so that the repository owner can set a default value for this setting effecting the *next* Release file, not the current one, which provides a functionality similar "HTTP Public Key Pinning". The pinning is in effect as long as the (then old) Release file is considered valid, but it is also ignored if the Release file has no Valid-Until at all. --- po/ku.po | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'po/ku.po') diff --git a/po/ku.po b/po/ku.po index f09cb16ed..60303c6e5 100644 --- a/po/ku.po +++ b/po/ku.po @@ -3062,14 +3062,9 @@ msgid "" "security purposes" msgstr "" -#: apt-pkg/deb/debmetaindex.cc -#, fuzzy, c-format -msgid "Invalid 'Date' entry in Release file %s" -msgstr "Pakêt nehate dîtin %s" - #: apt-pkg/deb/debmetaindex.cc #, c-format -msgid "Invalid 'Valid-Until' entry in Release file %s" +msgid "Invalid '%s' entry in Release file %s" msgstr "" #. TRANSLATOR: The first is an option name from sources.list manpage, the other two URI and Suite -- cgit v1.2.3