|
264.
|
|
|
Repository Configuration
|
|
|
type: Content of: <refentry><refsect1><title>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
apt-secure.8.xml
|
|
350.
|
|
|
Allow use of the internal TLS support in the http method. If set to false, this completely disables support for TLS in apt's own methods (excluding the curl-based https method). No TLS-related functions will be called anymore.
|
|
|
type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
apt.conf.5.xml
|
|
628.
|
|
|
The http scheme specifies an HTTP server for an archive and is the most commonly used method, with many options in the <literal>Acquire::http</literal> scope detailed in &apt-conf;. The URI can directly include login information if the archive requires it, but the use of &apt-authconf; should be preferred. The method also supports SOCKS5 and HTTP(S) proxies either configured via apt-specific configuration or specified by the environment variable <envar>http_proxy</envar> in the format (assuming an HTTP proxy requiring authentication) <replaceable>http://user:pass@server:port/</replaceable>. The authentication details for proxies can also be supplied via &apt-authconf;.
|
|
|
type: Content of: <refentry><refsect1><para><variablelist><varlistentry><listitem><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
sources.list.5.xml
|
|
629.
|
|
|
Note that these forms of authentication are insecure as the whole communication with the remote server (or proxy) is not encrypted so a sufficiently capable attacker can observe and record login as well as all other interactions. The attacker can <emphasis>not</emphasis> modify the communication through as APTs data security model is independent of the chosen transport method. See &apt-secure; for details.
|
|
|
type: Content of: <refentry><refsect1><para><variablelist><varlistentry><listitem><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
sources.list.5.xml
|
|
630.
|
|
|
The https scheme specifies an HTTPS server for an archive and is very similar in use and available options to the http scheme. The main difference is that the communication between apt and server (or proxy) is encrypted. Note that the encryption does not prevent an attacker from knowing which server (or proxy) apt is communicating with and deeper analyses can potentially still reveal which data was downloaded. If this is a concern the Tor-based schemes mentioned further below might be a suitable alternative.
|
|
|
type: Content of: <refentry><refsect1><para><variablelist><varlistentry><listitem><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
sources.list.5.xml
|
|
632.
|
|
|
The cdrom scheme allows APT to use a local CD-ROM, DVD or USB drive with media swapping. Use the &apt-cdrom; program to create cdrom entries in the source list.
|
|
|
type: Content of: <refentry><refsect1><para><variablelist><varlistentry><listitem><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
sources.list.5.xml
|
|
633.
|
|
|
The ftp scheme specifies an FTP server for an archive. Use of FTP is on the decline in favour of <literal>http</literal> and <literal>https</literal> and many archives either never offered or are retiring FTP access. If you still need this method many configuration options for it are available in the <literal>Acquire::ftp</literal> scope and detailed in &apt-conf;.
|
|
|
type: Content of: <refentry><refsect1><para><variablelist><varlistentry><listitem><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
sources.list.5.xml
|
|
634.
|
|
|
Please note that an FTP proxy can be specified by using the <envar>ftp_proxy</envar> environment variable. It is possible to specify an HTTP proxy (HTTP proxy servers often understand FTP URLs) using this environment variable and <emphasis>only</emphasis> this environment variable. Proxies using HTTP specified in the configuration file will be ignored.
|
|
|
type: Content of: <refentry><refsect1><para><variablelist><varlistentry><listitem><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
sources.list.5.xml
|
|
638.
|
|
|
APT can be extended with more methods shipped in other optional packages, which should follow the naming scheme <package>apt-transport-<replaceable>method</replaceable></package>. For instance, the APT team also maintains the package <package>apt-transport-tor</package>, which provides access methods for HTTP and HTTPS URIs routed via the Tor network.
|
|
|
type: Content of: <refentry><refsect1><para><variablelist><varlistentry><listitem><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
sources.list.5.xml
|
|
776.
|
|
|
This document provides an overview of how to use the APT package manager.
|
|
|
type: Content of: <book><bookinfo><abstract><para>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
guide.dbk
|