msgstr ""
"Project-Id-Version: apt-doc 1.0.5\n"
"Report-Msgid-Bugs-To: APT Development Team <deity@lists.debian.org>\n"
-"POT-Creation-Date: 2015-11-22 18:04+0100\n"
+"POT-Creation-Date: 2015-11-28 22:48+0100\n"
"PO-Revision-Date: 2015-01-27 14:11+0200\n"
"Last-Translator: Beatrice Torracca <beatricet@libero.it>\n"
"Language-Team: Italian <debian-l10n-italian@lists.debian.org>\n"
"<option>Trusted</option> (<option>trusted</option>) is a tri-state value "
"which defaults to APT deciding if a source is considered trusted or if "
"warnings should be raised before e.g. packages are installed from this "
-"source. This option can be used to override this decision either with the "
-"value <literal>yes</literal>, which lets APT consider this source always as "
-"a trusted source, even if it lacks or fails authentication checks, by "
-"disabling parts of &apt-secure;. It should therefore only be used in a local "
-"and trusted context (if at all) as otherwise security is breached. The "
-"opposite can be achieved with the value <literal>no</literal>, which causes "
-"the source to be handled as untrusted even if the authentication checks "
-"passed successfully. The default value can't be set explicitly."
+"source. This option can be used to override that decision. The value "
+"<literal>yes</literal> tells APT always to consider this source as trusted, "
+"even if it doesn't pass authentication checks. It disables parts of &apt-"
+"secure;, and should therefore only be used in a local and trusted context "
+"(if at all) as otherwise security is breached. The value <literal>no</"
+"literal> does the opposite, causing the source to be handled as untrusted "
+"even if the authentication checks passed successfully. The default value "
+"can't be set explicitly."
msgstr ""
#. type: Content of: <refentry><refsect1><para><itemizedlist><listitem><para>
projects / apt.git / blobdiff