On Thu 2016-09-01 16:28:44 -0400, Bitcoin Admin wrote:
> Yes, that 'other user' was me. And a fresh gnupg install solved the
> dilemma, just imported the keyring and trustdb
if you could send me a diff between your old gpg.conf and gpg-agent.conf
(the ones that don't work) and the new ones (that d
I found gpg-agent (gpg and gpg2 also) to be install in both /usr/bin &
/usr/local/bin directories
/usr/bin
-rwxr-xr-x 1 root root 195 Oct 16 2012 fix_gpg_badsig
-rwxr-xr-x 1 root root 1008632 Aug 18 13:54 gpg
-rwxr-xr-x 1 root root 917032 Apr 8 12:14 gpg2
-rwxr-xr-x 1
Yes, that 'other user' was me. And a fresh gnupg install solved the
dilemma, just imported the keyring and trustdb
I had to remove one other file pubring.kbx, as it conflicts with the
pubring.gpg
Give it a try.. and report back
Thomas
On 09/01/2016 10:08 PM, acubene+enigm...@vivaldi.net wrote:
>
OK thanks Ludwig
I'll try that
Le 01. 09. 16 à 22:06, Ludwig Hügelschäfer a écrit :
> On 01.09.16 21:25, acubene+enigm...@vivaldi.net wrote:
>
>> (...)
>> If I simply relaunch gpg-agent (without "--debug-level expert
>> --use-standard-socket --daemon /bin/sh") Enigmail still doesn't work.
>
> So
On 01.09.16 21:25, acubene+enigm...@vivaldi.net wrote:
> (...)
> If I simply relaunch gpg-agent (without "--debug-level expert
> --use-standard-socket --daemon /bin/sh") Enigmail still doesn't work.
Some days another user had the same problem on Ubuntu 16.04. He solved
it by starting over with a
Hi,
Whenever I try to read an encrypted e-mail I get the following error
message:
"GnuPG cannot query your passphrase via pinentry.
This is a system setup or configuration error that prevents Enigmail
from working properly and cannot be fixed automatically.
We strongly recommend that you consul
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 oth
On 01.09.16 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 oth
Hi,
On 01.09.16 14:14, Frederik Pascal Genreith wrote:
> Sehr geehrte Damen und Herren,
We're not so formal here on this mailing list ;-) And we're speaking in
english.
> ich versuche eine qualifizierte elektronische Signatur (QES) nach SigG
> in meine E-Mails einzubinden.
> Da ich bei Ihrem Thu
Hi again,
In fact, after verification, what worked was:
---
If necessary, edit/create ~/.gnupg/gpg-agent.conf and add one of the following
lines
pinentry-program /usr/bin/pinentry-curses
$ unset DISPLAY
---
https://ask.fedoraproject.org/en/question/32052/gpg2-problem-with-the-agent-no-pinentry/
Hi,
If your FAQ, on the webpage:
https://www.enigmail.net/index.php/en/faq?view=category&id=11#faqLink_2
In the section "Resolving issues with GnuPG 2.x and gpg-agent"
You forgot to talk about an error I just encountered, following the switch from
gpg1x to gpg2x: my drafts were automatically en
Sehr geehrte Damen und Herren,
ich versuche eine qualifizierte elektronische Signatur (QES) nach SigG
in meine E-Mails einzubinden.
Da ich bei Ihrem Thunderbird Add-On auch den Reiter "SmartCard" gefunden
habe, stellt sich mir die Frage, ob Sie QES unterstützen. Wenn ja,
benötige ich eine klassisc
12 matches
Mail list logo
