/usr/share/doc/gnupg
NameSizeModeActions
examples/-0755rm
changelog.Debian.gz18940644editdlrm
copyright105550644editdlrm
DCO12630644editdlrm
DETAILS.gz206460644editdlrm
FAQ2780644editdlrm
HACKING.gz71150644editdlrm
KEYSERVER30970644editdlrm
NEWS.Debian.gz6770644editdlrm
NEWS.gz460840644editdlrm
OpenPGP.gz22590644editdlrm
README.Debian14180644editdlrm
README.gz44790644editdlrm
THANKS.gz61900644editdlrm
TODO37980644editdlrm
TRANSLATE22300644editdlrm
Edit: /usr/share/doc/gnupg/README.Debian (1418B)
Using "Modern" GnuPG ==================== As of version 2.1.11-7+exp1, the gnupg package is provided by the "modern" version of GnuPG. This means: * supporting daemons are auto-launched as needed * all access to secret key material is handled by gpg-agent * all smartcard access is handled by scdaemon * all network access is handled by dirmngr * PGPv3 keys are no longer supported * secret keys are no longer stored in $GNUPGHOME/secring.gpg, but instead in $GNUPGHOME/private-keys-v1.d/ * public keyrings are stored in keybox format (~/.gnupg/pubring.kbx) by default for new users. Upgrading users will continue to use pubring.gpg until they decide to explicitly convert. Converting an existing installation ----------------------------------- If you have an existing GnuPG homedir from "classic" GnuPG, secret keys should be migrated automatically upon the first run of the "modern" version. If you have any secret keys that are stored only in a smartcard, after your first use of "modern" gpg you should insert the card and run: gpg --card-status (see https://bugs.debian.org/795881) Public keys will not be automatically migrated from pubring.gpg to pubring.kbx, however. If you want to migrate your public keyring, you can use a script like /usr/bin/migrate-pubring-from-classic-gpg -- Daniel Kahn Gillmor , Mon, 18 Apr 2016 19:08:36 -0400