Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

jetring(7) [debian man page]

JETRING(7)							 jetring commands							JETRING(7)

jetring - maintenance of gpg keyrings using changesets OVERVIEW
jetring is a collection of tools that allow for gpg keyrings to be maintained using changesets. It was developed with the Debian keyring in mind, and aims to solve the problem that a gpg keyring is a binary blob that's hard for multiple people to collaboratively edit. With jetring, changesets can be submitted, reviewed to see exactly what they will do, applied, and used to build a keyring. The origin of every change made to the keyring is available for auditing, and gpg signatures can be used to further secure things. OPERATION
A jetring directory is used as the "source" that a keyring is built from. To convert an existing gpg keyring to such a directory, use the jetring-explode(1) command. Each change to the gpg keyring is stored in a separate changeset file in the directory. Changesets can reflect any set of changes to the keyring. Changesets can also include arbitrary metadata. The jetring-gen(1) command can be used to compare two keyrings and generate a changeset from one to the other. Changesets are never removed or modified, only new ones added, using the jetring-accept(1) command. There's an ordering of the changesets. This ordering is stored in an index file. The index file is only appended to, to add new changesets. Changesets can be fully examined to see what change they make before applying them. The jetring-review(1) and jetring-diff(1) commands can be used for such review. To create a new keyring, or incrementally update an existing keyring, changesets are applied in order using the jetring-build(1) command. GPG SIGNATURES
The index file can optionally be gpg signed (the signature will be stored in index.gpg); if JETRING_SIGN is set to point to a gpg keyring, then jetring commands that operate on the jetring directory will always check that the index file is signed with one of the keys from that keyring. Commands that modify the index file will update its signature. CHANGESET FORMAT
A changeset file consists of one or more stanzas, separated by blank lines. The stanzas are in RFC-822-like format. Each stanza must have an action field, which specifies which action to take on the keyring, and a data field, typically a multi-line field, which contains the data to feed to the action. Supported actions are: import The data field should be an ascii-armored gpg key block, that is fed into gpg --import. edit-key keyid gpg --edit-key is run on the specified key id. The data field is a script, each line in it is passed in to gpg, the same as if gpg were being driven interactively. This can be used to make arbitrary changes to the key. delete-key keyid The given key is deleted. The data is fed into gpg --delete-key, and should be "y", since gpg expects that confirmation to deleting a key. Other fields can be added as desired to hold metadata about the change. Typical additional fields include date, changed-by, and comment. Changesets can be optionally have attached signatures, although such data is not automatically validated and is mostly useful to record who submitted or signed off on a given changeset. AUTHOR
Joey Hess, <>. JETRING(7)

Check Out this Related Man Page

DSCVERIFY(1)						      General Commands Manual						      DSCVERIFY(1)

dscverify - verify the validity of a Debian package SYNOPSIS
dscverify [--keyring keyring] ... changes_or_dsc_filename ... DESCRIPTION
dscverify checks that the GPG signatures on the given .changes or .dsc files are good signatures made by keys in the current Debian keyrings, found in the debian-keyring and debian-maintainers packages. (Additional keyrings can be specified using the --keyring option any number of times.) It then checks that the other files listed in the .changes or .dsc 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. OPTIONS
--keyring keyring Add keyring to the list of keyrings to be used. --no-default-keyrings 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 or .dsc files. --verbose Do not suppress GPG output. --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. 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. 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. Below is an example for an alias: alias dscverify='dscverify --keyring ~/.gnupg/pubring.gpg' STANDARD KEYRING LOCATIONS
By default dscverify searches for the debian-keyring in the following locations: - /org/ - /usr/share/keyrings/debian-keyring.gpg - /usr/share/keyrings/debian-maintainers.gpg SEE ALSO
gpg(1) and devscripts.conf(5). AUTHOR
dscverify was written by Roderick Schertler <> and posted on the mailing list, with several modifications by Julian Gilbey <>. DEBIAN
Debian Utilities DSCVERIFY(1)
Man Page

Featured Tech Videos