debsign - sign a Debian .changes and .dsc file pair using GPG
| Use Case | Command | Description |
|---|---|---|
| Sign a .changes file | debsign [options] changes-file | Sign .changes and referenced .dsc/.buildinfo files |
| Sign from remote machine | debsign -r user@host changes-file | Copy files to remote, sign, copy back |
| Specify signing key | debsign -k keyid changes-file | Use specific GPG key ID |
| Use custom GPG binary | debsign -p progname changes-file | Run progname instead of gpg |
| Source-only .changes | debsign -S | Look for source-only .changes file |
| Force re-sign | debsign --re-sign changes-file | Recreate signature even if already signed |
debsign [options] [changes-file|dsc-file|commands-file ...]
debsign mimics the signing aspects (and bugs) of dpkg-buildpackage(1). It takes a .dsc, .buildinfo, or .changes file and signs it, and any child .dsc, .buildinfo, or .changes files directly or indirectly referenced by it, using the GNU Privacy Guard. It is careful to calculate the size and checksums of any newly signed child files and replace the original values in the parent file.
If no file is specified, debian/changelog is parsed to determine the name of the .changes file to look for in the parent directory.
If a .commands file is specified it is first validated (see the details at ftp://ftp.upload.debian.org/pub/UploadQueue/README), and the name specified in the Uploader field is used for signing.
This utility is useful if a developer must build a package on one machine where it is unsafe to sign it; they need then only transfer the small .dsc, .buildinfo and .changes files to a safe machine and then use the debsign program to sign them before transferring them back. This process can be automated in two ways. If the files to be signed live on the remote machine, the -r option may be used to copy them to the local machine and back again after signing. If the files live on the local machine, then they may be transferred to the remote machine for signing using debrsign(1). However note that it is probably safer to have your trusted signing machine use debsign to connect to the untrusted non-signing machine, rather than using debrsign to make the connection in the reverse direction.
This program can take default settings from the devscripts configuration files, as described below.
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced in that order to set configuration variables. Command line options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently recognised variables are:
debrsign(1), debuild(1), dpkg-architecture(1), dpkg-buildpackage(1), gpg(1), gpg2(1), md5sum(1), sha1sum(1), sha256sum(1), scp(1), devscripts.conf(5)
This program was written by Julian Gilbey <jdg AT debian.org> and is copyright under the GPL, version 2 or later.
Generated by phpman v4.9.26-5-g7740029 Author: Che Dong Under GNU General Public License
2026-08-16 09:47 @2600:1f28:365:80b0:7cb9:fb:26c1:e368
CrawledBy CCBot/2.0 (https://commoncrawl.org/faq/)