Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

parcimonie(1p) [debian man page]

PARCIMONIE(1p)						User Contributed Perl Documentation					    PARCIMONIE(1p)

NAME
parcimonie - privacy-friendly helper to refresh a GnuPG keyring VERSION
Version 0.7.1 SYNOPSIS
parcimonie [options] DESCRIPTION
parcimonie is a daemon that slowly refreshes a GnuPG public keyring from a keyserver. Its refreshes one key at a time; between every key update, parcimonie sleeps a random amount of time, long enough for the previously used Tor circuit to expire. This process is meant to make it hard for an attacker to correlate the multiple performed key update operations. See the design.mdwn document to learn more about the threat and risk models parcimonie attempts to help coping with. USAGE
1. Configure GnuPG to be able to use a keyserver. You can skip this section if you already have configured a keyserver in ~/.gnupg/gpg.conf. Else, add to your gpg.conf something along these lines: keyserver hkp://keys.indymedia.org You obviously can choose your preferred keyserver here; if using hkps:// (which would be our second choice behind hkpms://), your GnuPG installation should support HPKS; on Debian systems, enabling such support is done by installing the gnupg-curl package; see those web pages for help with GnuPG hkps:// configuration: http://keys.mayfirst.org/ http://keys.indymedia.org/ You may want parcimonie to use a different keyserver than the one your usual GnuPG invocations do. This can be achieved by passing to parcimonie a command-line option such as: --gnupg-extra-arg "--keyserver=hkps://zimmermann.mayfirst.org" 2. Run "parcimonie --verbose". 3. Check the output for misconfiguration or bugs. 4. Once happy, start the daemon without the --verbose option. Note: the Debian package automatically starts the daemon with your X session. For example, GNOME users can configure its startup from the "System -> Preferences -> Startup Applications" menu. OPTIONS
The following command lists available options: parcimonie --help Tor configuration vs. --minimum-lapse-time In case you set the Tor MaxCircuitDirtiness setting yourself, you probably want to pass parcimonie a matching --minimum-lapse-time option so that subsequent key fetches use different Tor circuits. Just make sure this remains true: minimum-lapse-time >= Tor MaxCircuitDirtiness hkpms:// We recommend using hkpms; see http://web.monkeysphere.info/ for details. When a hkpms:// keyserver is being used, one needs to do two additional steps since gpgkeys_hkpms does not work in the torsocks wrapped environment parcimonie uses by default to run gpg. Torify gpgkeys_hkpms Just add the following line to gpg.conf: keyserver-options http-proxy=socks://127.0.0.1:9050 Hey, parcimonie, gpg is already torified Pass the --gnupg-already-torified switch to the parcimonie daemon command-line. parcimonie will then rely on the keyserver-options previously added to gpg.conf, and won't attempt to torify gpg connections itself. AUTHOR
intrigeri <intrigeri@boum.org> LICENSE AND COPYRIGHT
Copyright (C) 2010-2011 intrigeri <intrigeri@boum.org> Licensed under the same terms as Perl itself. BUGS
Please report any bugs or feature requests to "intrigeri at boum.org". SUPPORT
You can find documentation for parcimonie with the man command. man parcimonie You can also look for information at: o parcimonie's homepage <https://gaffer.ptitcanardnoir.org/intrigeri/code/parcimonie/> perl v5.14.2 2014-02-11 PARCIMONIE(1p)

Check Out this Related Man Page

GPG-PRESET-PASSPHRASE(1)					 GNU Privacy Guard					  GPG-PRESET-PASSPHRASE(1)

NAME
gpg-preset-passphrase - Put a passphrase into gpg-agent's cache SYNOPSIS
gpg-preset-passphrase [options] [command] cache-id DESCRIPTION
The gpg-preset-passphrase is a utility to seed the internal cache of a running gpg-agent with passphrases. It is mainly useful for unat- tended machines, where the usual pinentry tool may not be used and the passphrases for the to be used keys are given at machine startup. Passphrases set with this utility don't expire unless the --forget option is used to explicitly clear them from the cache --- or gpg-agent is either restarted or reloaded (by sending a SIGHUP to it). It is necessary to allow this passphrase presetting by starting gpg-agent with the --allow-preset-passphrase. gpg-preset-passphrase is invoked this way: gpg-preset-passphrase [options] [command] cacheid cacheid is either a 40 character keygrip of hexadecimal characters identifying the key for which the passphrase should be set or cleared. The keygrip is listed along with the key when running the command: gpgsm --dump-secret-keys. Alternatively an arbitrary string may be used to identify a passphrase; it is suggested that such a string is prefixed with the name of the application (e.g foo:12346). One of the following command options must be given: --preset Preset a passphrase. This is what you usually will use. gpg-preset-passphrase will then read the passphrase from stdin. --forget Flush the passphrase for the given cache ID from the cache. The following additional options may be used: -v --verbose Output additional information while running. -P string --passphrase string Instead of reading the passphrase from stdin, use the supplied string as passphrase. Note that this makes the passphrase visible for other users. SEE ALSO
gpg(1), gpgsm(1), gpg-agent(1), scdaemon(1) The full documentation for this tool is maintained as a Texinfo manual. If GnuPG and the info program are properly installed at your site, the command info gnupg should give you access to the complete manual including a menu structure and an index. GnuPG 2.0.15 2010-07-05 GPG-PRESET-PASSPHRASE(1)
Man Page