apt/doc/sources.list.5.xml, branch 1.3_exp1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3_exp12016-05-11T08:51:06ZRelease 1.3~exp12016-05-11T08:51:06ZJulian Andres Klodejak@debian.org2016-05-11T08:51:06Zurn:sha1:5b0577488ff60e7163fe7dc62a044329d398d726implement Identifier field for IndexTargets2016-05-08T16:15:28ZDavid Kalnischkiesdavid@kalnischkies.de2016-05-08T16:03:48Zurn:sha1:39c724b4848ef8d85c8c425f982dda85f0df1277
A frontend like apt-file is only interested in a specific set of files
and selects those easily via "Created-By". If it supports two locations
for those files through it would need to select both and a user would
need to know that implementation detail for sources.list configuration.
The "Identifier" field is hence introduced which by default has the same
value as "Created-By", but can be freely configured – especially it can
be used to give two indexes the same identifier.
support Signed-By in Release files as a sort of HPKP2016-05-01T08:50:24ZDavid Kalnischkiesdavid@kalnischkies.de2016-04-29T14:48:16Zurn:sha1:89901946f936446f439b95f1a9a85ac942ac2c92
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.
support multiple fingerprints in signed-by2016-05-01T08:50:24ZDavid Kalnischkiesdavid@kalnischkies.de2016-04-29T08:16:42Zurn:sha1:46e00c9062d09a642973e83a334483db1f310397
A keyring file can include multiple keys, so its only fair for
transitions and such to support multiple fingerprints as well.
change debian related entities to a more explicit name2016-01-14T16:33:58ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-14T15:11:28Zurn:sha1:9feb98eb0aeed775f78cb4afbf6bc0e3a90e9fed
Git-Dch: Ignore
release apt 1.12015-11-26T13:39:14ZMichael Vogtmvo@ubuntu.com2015-11-26T11:41:49Zurn:sha1:4c482ac554e1b533d98661de8585d5861d9ac562Fix missing </literal> in sources.list.5.xml page2015-11-26T11:39:06ZMichael Vogtmvo@ubuntu.com2015-11-26T11:39:06Zurn:sha1:286ea5c275ed692b738ac0e43ceb0936ffdf2468
Git-Dch: ignore
reword Trusted paragraph in sources.list(5)2015-11-26T11:16:44ZJustin B Ryejustin.byam.rye@gmail.com2015-11-26T11:16:44Zurn:sha1:b6f4e35ace11971d53179c111ec9de192523b090
Git-Dch: Ignore
update manpage last-modified from git via pre-export hook2015-11-25T14:20:10ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-22T18:02:13Zurn:sha1:ab5b1d0d31b2fbdc4896f8a107611ff056d6a668
Never updating this information is wrong, updating it automatically
isn't super correct either, but it seems conventional to have it and
updating it more often than needed seems better than updating it never.
Git-Dch: Ignore
review sources.list(5) manpage2015-11-25T14:20:10ZJustin B Ryejustin.byam.rye@gmail.com2015-11-22T13:29:49Zurn:sha1:906ce854c6f27c9ee7ed209de05321c2027ae0b5