&apt-email;
&apt-product;
<!-- The last update date -->
- <date>2016-05-27T00:00:00Z</date>
+ <date>2016-08-05T00:00:00Z</date>
</refentryinfo>
<refmeta>
Allow update operations to load data files from
repositories without sufficient security information.
The default value is "<literal>false</literal>".
- Concept and implications of this are detailed in &apt-secure;.
+ Concept, implications as well as alternatives are detailed in &apt-secure;.
+ </para></listitem>
+ </varlistentry>
+
+ <varlistentry><term><option>AllowWeakRepositories</option></term>
+ <listitem><para>
+ Allow update operations to load data files from
+ repositories which provide security information, but these
+ are deemed no longer cryptographically strong enough.
+ The default value is "<literal>false</literal>".
+ Concept, implications as well as alternatives are detailed in &apt-secure;.
</para></listitem>
</varlistentry>
for a previously trusted repository apt will refuse the update. This
option can be used to override this protection. You almost certainly
never want to enable this. The default is <literal>false</literal>.
-
- Note that apt will still consider packages from this source
- untrusted and warns about them if you try to install them.
+ Concept, implications as well as alternatives are detailed in &apt-secure;.
</para></listitem>
</varlistentry>
<title>Periodic and Archives options</title>
<para><literal>APT::Periodic</literal> and <literal>APT::Archives</literal>
groups of options configure behavior of apt periodic updates, which is
- done by the <literal>/etc/cron.daily/apt</literal> script. See the top of
+ done by the <literal>/usr/lib/apt/apt.systemd.daily</literal> script. See the top of
this script for the brief documentation of these options.
</para>
</refsect1>