<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/doc/apt.conf.5.xml, branch 1.6_rc1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.6_rc1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.6_rc1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2018-04-15T20:13:04Z</updated>
<entry>
<title>Release 1.6~rc1</title>
<updated>2018-04-15T20:13:04Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-04-15T20:05:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=73c5027cf8ceabf7bb72fe08d4d86d07d3d72461'/>
<id>urn:sha1:73c5027cf8ceabf7bb72fe08d4d86d07d3d72461</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release 1.6~beta1</title>
<updated>2018-02-26T12:15:26Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-02-26T12:15:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5206249ea92fccf9e812a2d373cbd2f16c623059'/>
<id>urn:sha1:5206249ea92fccf9e812a2d373cbd2f16c623059</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Check that Date of Release file is not in the future</title>
<updated>2018-02-19T15:05:01Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-01-29T15:15:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9e5899cac1a6367e3769af52a724821880e538f6'/>
<id>urn:sha1:9e5899cac1a6367e3769af52a724821880e538f6</id>
<content type='text'>
By restricting the Date field to be in the past, an attacker cannot
just create a repository from the future that would be accepted as
a valid update for a repository.

This check can be disabled by Acquire::Check-Date set to false. This
will also disable Check-Valid-Until and any future date related checking,
if any - the option means: "my computers date cannot be trusted."

Modify the tests to allow repositories to be up to 10 hours in the
future, so we can keep using hours there to simulate time changes.
</content>
</entry>
<entry>
<title>Release 1.6~alpha7</title>
<updated>2018-01-18T14:47:08Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-01-18T14:47:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=70e68ed87d8ecd011df80f00c6b8ff6316e2b413'/>
<id>urn:sha1:70e68ed87d8ecd011df80f00c6b8ff6316e2b413</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release 1.6~alpha6</title>
<updated>2018-01-03T22:35:18Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2018-01-03T22:35:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a283107760379b869b9b730e03b9d2d4aac4e736'/>
<id>urn:sha1:a283107760379b869b9b730e03b9d2d4aac4e736</id>
<content type='text'>
</content>
</entry>
<entry>
<title>document https options in new apt-transport-https manpage</title>
<updated>2018-01-03T17:55:41Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-11-22T23:58:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c28682430a27f75ceb8cc8dff78b3a560fd68399'/>
<id>urn:sha1:c28682430a27f75ceb8cc8dff78b3a560fd68399</id>
<content type='text'>
Same reasoning as with the previous commit for http with the added
benefit of moving the hard to discover and untranslated example config
into a manpage which could be translated.
</content>
</entry>
<entry>
<title>document http options in new apt-transport-http manpage</title>
<updated>2018-01-03T17:55:41Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-11-22T18:39:31Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=956145444e1a3b7f5e660f71904711f4ea5bd262'/>
<id>urn:sha1:956145444e1a3b7f5e660f71904711f4ea5bd262</id>
<content type='text'>
We had documentation for the http transport in our "catch-all" apt.conf
manpage, but it seems benefitial to document transports in their own
manpage instead of pushing them all into one.
</content>
</entry>
<entry>
<title>Upload 1.5~alpha1 to experimental</title>
<updated>2017-06-28T17:53:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-28T17:53:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c9390165718d4cf0ec43a0af01f06d6628717905'/>
<id>urn:sha1:c9390165718d4cf0ec43a0af01f06d6628717905</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Introduce Acquire::AllowTLS to turn off TLS support</title>
<updated>2017-06-28T15:34:51Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-28T15:17:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=147ac0fc90d972a11f5e91521ba3d385015b5945'/>
<id>urn:sha1:147ac0fc90d972a11f5e91521ba3d385015b5945</id>
<content type='text'>
As requested by Henrique de Moraes Holschuh, here comes
an option to disable TLS support. If the option is set
to false, the internal TLS layer is disabled.
</content>
</entry>
<entry>
<title>Release 1.4~beta1</title>
<updated>2016-11-25T22:50:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-11-25T22:47:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7d5234ab88b4cd6b172f13d0912c585983c3410b'/>
<id>urn:sha1:7d5234ab88b4cd6b172f13d0912c585983c3410b</id>
<content type='text'>
</content>
</entry>
</feed>
