blob: b9ef9aa565dbe842fb5db7ab2e41718df20c3544 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
<!-- -*- mode: sgml; mode: fold -*- -->
<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
<!ENTITY % aptent SYSTEM "apt.ent">
%aptent;
]>
<refentry>
&apt-docinfo;
<refmeta>
<refentrytitle>vendors.list</>
<manvolnum>5</>
</refmeta>
<!-- Man page title -->
<refnamediv>
<refname>vendors.list</>
<refpurpose>Security key configuration for APT</>
</refnamediv>
<RefSect1><Title>Description</>
<para>
The package vendor list contains a list of all vendors
from whom you wish to authenticate downloaded packages.
For each vendor listed, it must contain the corresponding
PGP key fingerprint, so that APT can perform signature
verification of the release file and subsequent checking
of the checksums of each downloaded package.
To have authentication enabled, you must add the
vendor identification string (see below) enclosed in
square braces to the sources.list line for all sites that mirror
the repository provided by that vendor.
<para>
The format of this file is similar to the one used by
apt.conf. It consists of an arbitrary number of blocks of
vendors, where each block starts with a string telling the
<replaceable/key_type/ and the <replaceable/vendor_id/.
<para>
Some vendors may have multiple blocks that define different
security policies for their distributions. Debian for instance
uses a different signing methodology for stable and unstable releases.
<para>
<replaceable/key_type/ is the type of the check required.
Currently, there is only one type available which is
<literal/simple-key/.
<para>
<replaceable/vendor_id/ is the vendor identification string. It is an
arbitrary string you must supply to uniquely identifify a
vendor that's listed in this file.
Example:
<informalexample><programlisting>
single_key "joe"
{
Fingerprint "0987AB4378FSD872343298787ACC";
Name "Joe Shmoe <joe@shmoe.com>";
}
</programlisting></informalexample>
</RefSect1>
<RefSect1><Title>The simple-key type</>
<para>
This type of verification is used when the vendor has a single
secured key that must be used to sign the Release file. The
following items should be present
<VariableList>
<VarListEntry><Term>Fingerprint</Term>
<ListItem><Para>
The PGP fingerprint for the key. The fingerprint should be
expressed in the standard notion with or without spaces.
The <option/--fingerprint/ option for
<CiteRefEntry><RefEntryTitle><command/gpg/</RefEntryTitle><ManVolNum/1/</CiteRefEntry>
will show the fingerprint for the selected keys(s).
</VarListEntry>
<VarListEntry><Term>Name</Term>
<ListItem><Para>
A string containing a description of the owner of
the key or vendor. You may put the vendor name and it's
email. The string must be quoted with ".
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1><Title>Files</>
<para>
<filename>/etc/apt/vendors.list</>
</RefSect1>
<RefSect1><Title>See Also</>
<para>
&sources-list;
</RefSect1>
&manbugs;
&manauthor;
</refentry>
|
