On 2016-09-01 at 14:42, Guillaume MULLER wrote: > I'm not sure if I made a mistake when switching from gpg to gpg2, or if it is > a bug in gpg2, or if there was a tool in enigmail to switch to gpg2, which > forgot to export/import the secret keys, but I think it would save a lot of > time to other people like me if you would mention the problem/solution in > your FAQ! >
Versions of GnuPG modern branch (2.1.0 and later) use a different way to store private keys, so not all cases where you use `gpg2` will have that problem, if you have stable branch (2.0.x). Although it would be a QoL thing for Enigmail to add that, it was explained way back when 2.1.0 was released. Hopefully more and more distros reprecate the 'gpg' and 'gpg2' package mix, or follow Debian's way of having GnuPG 1.x as an optional package called 'gnupg1' while having GnuPG >=2.1 as 'gpg'. -- Juan Miguel Navarro Martínez GPG Keyfingerprint: 5A91 90D4 CF27 9D52 D62A BC58 88E2 947F 9BC6 B3CF _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
