DEBSIGS(1)
π DEBSIGS(1) β like, the whole manual page, bestie
okay so real talk: this is debsigs, a Perl script from the User Contributed Perl Documentation collection, and it's the one that puts signatures into .deb files. Sit down, hydrate, and let's go π«Ά
πΈ NAME πΈ
debsigs β the girl who processes signatures in .deb packages. that's it, that's the whole job description β¨
π SYNOPSIS π
Like, here's exactly how you call her. verbatim, no notes:
debsigs --list|-l [-v] file [file...]
debsigs --sign=type [--default-key=keyID] [-v] file [file...]
debsigs --verify|--check|-c file [file...]
debsigs --delete=type file [file...]
π¦ DESCRIPTION π¦
So debsigs is the tool you use to manipulate the cryptographic signatures stored inside a .deb file. Manipulate. not verify. huge difference, iykyk π
She is not the one who checks whether those signatures are valid β that is literally somebody else's whole personality. For that, go see debsig-verify(1). periodt.
β¨ OPTIONS β¨
every single flag, present and accounted for. no gatekeeping here π
--list,-lor-tβ lists the signatures found in the specified file. a little signature show-and-tell π--sign=typeβ creates a new signature of the type you specify in the given file. it gets created using the default key for your GPG keyring. for the possible values oftype, scroll down to "SIGNATURE TYPES" π--default-key=keyIDβ uses a key other than the default for signing the package. main character key energy π--secret-keyring=fileor-Kfileβ uses a keyring other than the default for signing the package. this option gets passed along to GPG verbatim β like, she doesn't touch it, she just hands it over β so check the discussion in thegpg(1)manpage for how to specify the keyring file ποΈ-vβ displays verbose output. she will tell you everything π¬--verifyor--checkor-cβ invokesdebsig-verifyto check the validity of the signature on this package. yes, this is the one that calls the other girl π--delete=typeβ deletes the signature of the specified type from the package. gone. blocked. unfollowed π
π SIGNATURE TYPES π
A Debian package can carry different types of signatures β she contains multitudes. the most commonly-used ones are:
originβ the official signature of the organization which distributes the package, usually the Debian Project or a GNU/Linux distribution derived from it. this signature may be added automatically β¨maintβ the signature of the maintainer of the Debian package. this signature should be added by the maintainer before uploading the package. do your homework, bestie πarchiveβ an automatically-added signature renewed periodically to ensure that a package downloaded from an online archive is indeed the latest version distributed by the organization. keeping it fresh π§
also, like, go read the /usr/share/doc/debsigs/signing-policy.txt file for more info and the rationale behind the different signature types. it's giving lore π
β FUTURE DIRECTIONS β
ngl it would be nice to have a command-line option to change the command used for signing, instead of hard-coding gpg. like... imagine the flexibility. one day πΈ
π AUTHOR π
John Goerzen <jgoerzen@progenylinux.com> β the icon, the legend, the actual author π«Ά
π₯ SEE ALSO π₯
debsig-verify(1), gpg(1) β go read those too, they're in the group chat π¬
okay that's the whole page!! mwah π
and for the credits scroll, since you know I'd never leave her hanging: this beauty is perl v5.42.3, dated 1980-01-01. vintage. iconic. no cap πβ¨π
π¦ where this page comes from
- nixos 26.05: perl5.42.3-debsigs 0.2.2
- nixpkgs unstable: perl5.42.3-debsigs 0.2.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms