DSCVERIFY(1)

πŸ’– DSCVERIFY(1) β€” like, the manual page bestie πŸ’–

General Commands Manual · the one and only dscverify ✨


🌸 NAME 🌸

dscverify β€” verify the validity of a Debian package. yes girl, it's the vibe checker for your packages 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

dscverify [--keyring keyring] ... changes_or_buildinfo_or_dsc_filename
...

So basically you hand it one or more files and it does its little check thing. One or many, it don't care. πŸ’…


✨ DESCRIPTION ✨

okay so here's the tea β˜•: dscverify checks that the GPG signatures on the given .changes, .buildinfo or .dsc files are good signatures made by keys in the current Debian keyrings, and those keyrings live in the debian-keyring and debian-tag2upload-keyring packages. (oh, and bestie β€” you can add MORE keyrings with the --keyring option, like, as many times as you want, go off)

Then, once the signatures pass the vibe check πŸŽ€, it checks that all the other files listed in the .changes, .buildinfo or .dsc files have the correct sizes and checksums β€” that's MD5 plus SHA1 and SHA256 if the latter are present. iykyk.

The exit status is 0 if there are no problems and non-zero otherwise. no cap, non-zero means something is wrong and we do not stan that. 😭


πŸ‘‘ OPTIONS πŸ‘‘

  • --keyring keyring β€” adds keyring to the list of keyrings to be used. stack 'em up, icon πŸ’…
  • --no-default-keyrings β€” do not use the default set of keyrings. bye defaulties πŸ‘‹
  • --no-conf, --noconf β€” do not read any configuration files. πŸš«πŸ“„ heads up tho: this can only be used as the FIRST option given on the command-line. like it has to go first or it does not count, periodt.
  • --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. (sig step? skipped. checksums? still doing their thing.)
  • --verbose β€” do not suppress GPG output. let it yap πŸ—£οΈβœ¨
  • --help, -h β€” display a help message and exit successfully. 🫢
  • --version β€” display version and copyright information and exit successfully. πŸ’œ

🧚 CONFIGURATION VARIABLES 🧚

The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables. order matters bestie, it's literally in that order. Environment variable settings are ignored for this purpose. πŸ™ˆ

If the first command line option given is --noconf or --no-conf, then these files will not be read. (first option. only. we said what we said. πŸ’…)

The currently recognised variable is:

  • DSCVERIFY_KEYRINGS β€” this is a colon-separated list of extra keyrings to use in addition to any specified on the command line. πŸŽ€βœ¨

🌈 KEYRING 🌈

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. you got options, bestie, and both of them slay. πŸ’–

Below is an example for an alias:

alias dscverify='dscverify --keyring ~/.gnupg/pubring.gpg'

put that in your shell rc and never think about it again, that's the dream. πŸ¦‹


⭐ STANDARD KEYRING LOCATIONS ⭐

By default dscverify searches for the debian-keyring in the following locations:

  • ~/.gnupg/trustedkeys.gpg
  • /srv/keyring.debian.org/keyrings/debian-keyring.gpg
  • /usr/share/keyrings/debian-keyring.gpg
  • /usr/share/keyrings/debian-tag2upload.pgp
  • /usr/share/keyrings/debian-maintainers.gpg
  • /usr/share/keyrings/debian-nonupload.gpg

like a little scavenger hunt, but make it keyrings πŸ”πŸ’…


πŸ’œ SEE ALSO πŸ’œ

gpg(1), devscripts.conf(5)

go read those too, they're giving main character energy fr fr πŸ“šβœ¨


πŸŽ€ AUTHOR πŸŽ€

dscverify was written by Roderick Schertler <roderick@argon.org> and posted on the debian-devel@lists.debian.org mailing list, with several modifications by Julian Gilbey <jdg@debian.org>.

legends, both of them, we love to see it πŸ‘‘


and that's the whole page bestie!! this one comes from the Debian Utilities corner of the DEBIAN world β€” DSCVERIFY(1) β€” so go verify something and slay πŸ’…βœ¨

πŸ“¦ where this page comes from