In fact, I was wrong...

Somehow, I had a small timelaps in which the Enigmail plugin started to
work again as previously but after a restart of the computer (the day
after) I went back to the problem.

Unfortunately, I have no explanation at all about this behavior...
(and I am really sorry for that!).

On 08/19/2015 10:45 AM, Daniel Kahn Gillmor wrote:
> On Wed 2015-08-19 00:04:48 +0200, Emmanuel Fleury wrote:
>> I found a better way to fix it (and keep the last GPG 2.1.7-2 package).
>> I seems that installing the last GPG package change slightly the content
>> of the directory ~/.gnupg/.
>> Here is the way to do it:
>> - In Iceweasel, go to the menu item:
>>   Enigmail -> Key management
>> - Select your own key.
>> - Go to the menu: File->Import Keys from File
>> - Select the file ~/.gnupg/secring.gpg
>> Now, the Enigmail plugin seems to work properly...
> this suggests that you think the secret keyring was not migrated
> properly during the 2.0 to 2.1 transition.  If this is the case, it will
> be a problem without enigmail in the loop at all (just with gpg2 on the
> command line).
> Are you using your key on a smartcard?  if so, maybe you ran into the
> same issue as #795881 ?
> The fact that your problem sounds like it's still unresolved (from your
> subsequent message) sounds like this isn't the core of it still.
> I'm still unable to reproduce the problem you and the original reporter
> are describing :/ Any help in reproducing it would be welcome.
>> It seems that the root of the problem is coming from the changes that
>> are made in the files in the ~/.gnupg files and the fact that the
>> Enigmail plugin is not aware of this change (and especially this
>> relocation of the private keys).
> Enigmail shouldn't need to be aware of the change, the secret key
> migration should happen automatically.
>           --dkg

Attachment: signature.asc
Description: OpenPGP digital signature

Pkg-mozext-maintainers mailing list

Reply via email to