dscverify - verify the validity of a Debian package
checks that the GPG signatures on the given .changes
files are good signatures made by keys in the
current Debian keyrings, found in the debian-keyring
(Additional keyrings can be specified using the --keyring
number of times.) It then checks that the other files listed in the
files have the correct sizes
and checksums (MD5 plus SHA1 and SHA256 if the latter are present). The exit
status is 0 if there are no problems and non-zero otherwise.
- --keyring keyring
- Add keyring to the list of keyrings to be used.
- Do not use the default set of keyrings.
- --no-conf, --noconf
- Do not read any configuration files. This can only be used
as the first option given on the command-line.
- --nosigcheck, --no-sig-check, -u
- Skip the signature verification step. That is, only verify
the sizes and checksums of the files listed in the .changes,
.buildinfo or .dsc files.
- Do not suppress GPG output.
- --help, -h
- Display a help message and exit successfully.
- Display version and copyright information and exit
The two configuration files /etc/devscripts.conf
are sourced by a shell in that order to set configuration variables.
Environment variable settings are ignored for this purpose. If the first
command line option given is --noconf
, then these
files will not be read. The currently recognised variable is:
- This is a colon-separated list of extra keyrings to use in
addition to any specified on the command line.
Please note that the keyring provided by the debian-keyring package can be
slightly out of date. The latest version can be obtained with rsync, as
documented in the README that comes with debian-keyring. If you sync the
keyring to a non-standard location (see below), you can use the possibilities
to specify extra keyrings, by either using the above mentioned configuration
option or the --keyring option.
Below is an example for an alias:
alias dscverify='dscverify --keyring ~/.gnupg/pubring.gpg'
By default dscverify searches for the debian-keyring in the following locations:
was written by Roderick Schertler <email@example.com>
and posted on the firstname.lastname@example.org mailing list, with several
modifications by Julian Gilbey <email@example.com>.