vendors.list.5.sgml 3.1 KB

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