gpg split - qube doesn't see key pair - only public key
44 views
Skip to first unread message
zabo...@gmail.com
Aug 29, 2016, 5:01:18 PM8/29/16
to qubes-users
I've been using GPG split for over a year with keys that hadn't been generated and were only imported into the vault qube and never had a problem.
Yesterday I generated a GPG key pair in the vault qube, and while the vault qube has no problem in seeing the private key, enigmail in a different qube only sees a public key.
Has anyone ever experienced this? I've been looking for similar problems both here and elsewhere and found no reference to this.
Thanks for your help.
rz
Andrew David Wong
Aug 30, 2016, 2:38:30 AM8/30/16
to zabo...@gmail.com, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Changes to private keys with GnuPG 1 are not visible to GnuPG 2, and
vice versa. So, if you generated your key with the `gpg` command
(instead of `gpg2`), then Enigmail probably isn't seeing it because it
and Split GPG are using gpg2.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXxSncAAoJENtN07w5UDAwuIQP+gNLfTL14OUm5umcoYsqMCO1
ON494YjQLk1JBTDS2tO28psDq5/4g6iYTHAdgf9JprcJquHArBxVrRFihrxdiq88
P2g5aN5+7nXUlHxOiDSrAz634aGVlx+19m+6VXm5E37qvUjrSfh0bN9fCwoWEvTJ
XzrPRMhqPnsvERwNgSoWuHvZ6AobZwQ3EVM355UdM49r36zHlLBUb8yHkQnYs02U
V4+MDS4gB9ytaECVD37n/HlrZ4c6DNXEIemN51sQ18iL7PUSIXqMSZBtFizwTibV
Yo4oeCkOFRSqRkhcO77hQ8TDGwjhi/lCk5eNVnAaG8mA52/wqznkrzv3RaEy7NgM
eQriG/BfvfZemx+W8MSvgr//cFX31PGpQpXiWL1mA7F8o2FLVuY6dXmaSL8jnu/B
JqLcNSzryJUlQU/u1VzU/aD9aI7FIl0Syn0esjzwEMCsuSkT7q93YW126n7BADtS
laVq2g5v6UuuZpGIBOuC7wgcZF02Yc/kwS7EnFX4pqZgm2mP1H8XKmWm5o9siSqH
IeEee6YN86x0B2iZfIjds4HLGlrZ5zk5iftFd8Yy1CXUvre7P156j8MOhlgJwnHQ
IjhMNOYrEokRyXqolW1+j68wvoJ5ro1u/ZHm58rwBZoHqW+PdIg8dpca8l7QFv1W
aylflqGaMZmqQ/jK6BCL
=ukrT
-----END PGP SIGNATURE-----
Hash: SHA512
vice versa. So, if you generated your key with the `gpg` command
(instead of `gpg2`), then Enigmail probably isn't seeing it because it
and Split GPG are using gpg2.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXxSncAAoJENtN07w5UDAwuIQP+gNLfTL14OUm5umcoYsqMCO1
ON494YjQLk1JBTDS2tO28psDq5/4g6iYTHAdgf9JprcJquHArBxVrRFihrxdiq88
P2g5aN5+7nXUlHxOiDSrAz634aGVlx+19m+6VXm5E37qvUjrSfh0bN9fCwoWEvTJ
XzrPRMhqPnsvERwNgSoWuHvZ6AobZwQ3EVM355UdM49r36zHlLBUb8yHkQnYs02U
V4+MDS4gB9ytaECVD37n/HlrZ4c6DNXEIemN51sQ18iL7PUSIXqMSZBtFizwTibV
Yo4oeCkOFRSqRkhcO77hQ8TDGwjhi/lCk5eNVnAaG8mA52/wqznkrzv3RaEy7NgM
eQriG/BfvfZemx+W8MSvgr//cFX31PGpQpXiWL1mA7F8o2FLVuY6dXmaSL8jnu/B
JqLcNSzryJUlQU/u1VzU/aD9aI7FIl0Syn0esjzwEMCsuSkT7q93YW126n7BADtS
laVq2g5v6UuuZpGIBOuC7wgcZF02Yc/kwS7EnFX4pqZgm2mP1H8XKmWm5o9siSqH
IeEee6YN86x0B2iZfIjds4HLGlrZ5zk5iftFd8Yy1CXUvre7P156j8MOhlgJwnHQ
IjhMNOYrEokRyXqolW1+j68wvoJ5ro1u/ZHm58rwBZoHqW+PdIg8dpca8l7QFv1W
aylflqGaMZmqQ/jK6BCL
=ukrT
-----END PGP SIGNATURE-----
reginazabo
Aug 30, 2016, 6:52:38 AM8/30/16
to qubes-users
Il giorno martedì 30 agosto 2016 08:38:30 UTC+2, Andrew David Wong ha scritto:
> Changes to private keys with GnuPG 1 are not visible to GnuPG 2, and
> vice versa. So, if you generated your key with the `gpg` command
> (instead of `gpg2`), then Enigmail probably isn't seeing it because it
> and Split GPG are using gpg2.
thank you! that was exactly the problem.> Changes to private keys with GnuPG 1 are not visible to GnuPG 2, and
> vice versa. So, if you generated your key with the `gpg` command
> (instead of `gpg2`), then Enigmail probably isn't seeing it because it
> and Split GPG are using gpg2.
Reply all
Reply to author
Forward
0 new messages