<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/methods, branch 1.5_alpha2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.5_alpha2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.5_alpha2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2017-06-29T14:12:40Z</updated>
<entry>
<title>http: Only use system CA store if CaInfo is not set</title>
<updated>2017-06-29T14:12:40Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-29T13:30:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=58a1a72988e9280343821243217c1fc7d5ddea46'/>
<id>urn:sha1:58a1a72988e9280343821243217c1fc7d5ddea46</id>
<content type='text'>
It turns out that curl only sets the system trust store if
the CaInfo option is not set, so let's do the same here.
</content>
</entry>
<entry>
<title>Improve error message if system CA store is empty</title>
<updated>2017-06-29T10:54:30Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-29T10:47:55Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5e9c1b36764109ab13232188892730c326fb41e8'/>
<id>urn:sha1:5e9c1b36764109ab13232188892730c326fb41e8</id>
<content type='text'>
Tell the user to install ca-certificates.

Closes: #866377
</content>
</entry>
<entry>
<title>use port from SRV record instead of initial port</title>
<updated>2017-06-28T23:23:59Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-06-28T20:56:27Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9bdc09016f9570389451dd619d7e878bfeaa91df'/>
<id>urn:sha1:9bdc09016f9570389451dd619d7e878bfeaa91df</id>
<content type='text'>
An SRV record includes a portnumber to use with the host given, but apt
was ignoring the portnumber and instead used either the port given by
the user for the initial host or the default port for the service.

In practice the service usually runs on another host on the default
port, so it tends to work as intended and even if not and apt can't get
a connection there it will gracefully fallback to contacting the initial
host with the right port, so its a user invisible bug most of the time.
</content>
</entry>
<entry>
<title>support tor+https being handled by http</title>
<updated>2017-06-28T20:26:56Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-06-28T20:20:22Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=579f8f1008eceecd3da9ac53923c6a8d08244cb7'/>
<id>urn:sha1:579f8f1008eceecd3da9ac53923c6a8d08244cb7</id>
<content type='text'>
The apt-transport-tor package operates via simple symlinks which can
result in 'http' being called as 'tor+https', so it must pick up the
right configuration pieces and trigger https support also in plus names.
</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>Fix https-&gt;http redirect issues</title>
<updated>2017-06-28T13:52:38Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-06-28T13:52:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=29a08d8ab0c4d82f26c2712c456508784040cdbb'/>
<id>urn:sha1:29a08d8ab0c4d82f26c2712c456508784040cdbb</id>
<content type='text'>
Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>methods: http: Drain pending data before selecting</title>
<updated>2017-06-28T13:52:38Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-28T11:20:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f806530b9ea858ca6bda8fb8f43d988aba02dab3'/>
<id>urn:sha1:f806530b9ea858ca6bda8fb8f43d988aba02dab3</id>
<content type='text'>
GnuTLS can already have data pending in its buffers, we need
to to drain that first otherwise select() might block
indefinitely.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>Allow building without curl</title>
<updated>2017-06-28T13:52:38Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-27T22:12:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0fe2161020d6e331639ed11872a947dd20035890'/>
<id>urn:sha1:0fe2161020d6e331639ed11872a947dd20035890</id>
<content type='text'>
This makes testing easier and prepares us for the
transition.
</content>
</entry>
<entry>
<title>methods: Add HTTPS support to http method, using GnuTLS</title>
<updated>2017-06-28T13:52:38Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-28T08:55:57Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2851ec6cf037d552118b885be0dd7796d74730c6'/>
<id>urn:sha1:2851ec6cf037d552118b885be0dd7796d74730c6</id>
<content type='text'>
The http method will eventually replace the curl-based
https method, but for now, this is an opt-in experiment
that can be enabled by setting Dir::Bin::Methods::https
to "http".

Known issues:
- We do not support HTTPS proxies yet
- We do not support proxying HTTPS connections yet (CONNECT)
- IssuerCert and SslForceVersion are unsupported

Gbp-Dch: Full
</content>
</entry>
<entry>
<title>methods: connect: Switch from int fds to new MethodFd</title>
<updated>2017-06-28T13:52:38Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-28T08:55:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5666084ecfe140aaa3f89388de557c2f875b4244'/>
<id>urn:sha1:5666084ecfe140aaa3f89388de557c2f875b4244</id>
<content type='text'>
Use std::unique_ptr&lt;MethodFd&gt; everywhere we used an
integer-based file descriptor before. This allows us
to implement stuff like TLS support easily.

Gbp-Dch: ignore
</content>
</entry>
</feed>
