On Monday, March 26, 2018 at 4:16:10 PM UTC-4, regina zabo wrote:
> After the update of Enigmail to version 2.0, split-gpg has stopped working - 
> the work qube still tries to access the vault, with the usual prompt asking 
> for permission to access the vault, but then the prompt with the passphrase 
> does not appear and I find no way of forcing the decryption manually through 
> thunderbird+enigmail.
> 
> I've tried with Thunderbird version 52.6.0 on Debian 9 and Thunderbird 
> version 52.4.0 on Fedora 25.
> The vault is based on Fedora 25, but I've also tried running it on the Debian 
> 9 template and nothing changed.
> 
> Also de-activating PEP and Autocrypt doesn't seem to work.

I too am experiencing the same thing. Thunderbird automatically updated 
Enigmail to version 2.0 and now split gpg is not working. I opened up the 
Enigmail console and it is using the wrapper, but nothing is happening:

Initializing Enigmail service ...
EnigmailAgentPath=/usr/bin/qubes-gpg-client-wrapper

enigmail> /usr/bin/qubes-gpg-client-wrapper --batch --no-tty --charset utf-8 
--display-charset utf-8 --version --version
gpg (GnuPG) 2.2.5
libgcrypt 1.8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/user/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

enigmail> /usr/bin/gpgconf --list-dirs
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset 
utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --with-fingerprint 
--fixed-list-mode --with-colons --list-keys
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset 
utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --with-fingerprint 
--fixed-list-mode --with-colons --list-secret-keys
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset 
utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --sender 
eric@EDITED --max-output 149800 --decrypt
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset 
utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --with-fingerprint 
--fixed-list-mode --with-colons --list-keys
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset 
utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --with-fingerprint 
--fixed-list-mode --with-colons --list-secret-keys

Enigmail is using the qubes-gpg-client-wrapper, but nothing is happening and I 
am not sure where to look next to see why this is the case.

I, too, am interested in a solution.

Eric

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/31190161-eb83-47f6-bd66-832614fbff57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to