-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Enigmail user ;-)
> Do I need to send my public key to the key servers again now?
yes
Olav
- --
The Enigmail Project - OpenPGP Email Security For Mozilla Applications
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Dies ist eine elekt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 3/21/2015 11:44, Onno Ekker wrote:
> On 21-3-2015 16:39, Enigmail User wrote:
>> On 3/21/2015 06:36, Olav Seyfarth wrote:
>>> Hi Patrick,
>>
I'm thinking about adding "--allow-weak-digest-algos" to the
GnuPG parameters if GnuPG > 2.0.27
> the point was: is it possible to further use a key that has/had MD5 and now
> throws a warning by modifying it. If not, then the only way seems to be to
> delete the key - if one doesn't want to /allow-weak-digest-algos/ .
D'oh -- my bad.
By "old key" I thought the poster meant, you know, an ol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Robert,
the point was: is it possible to further use a key that has/had MD5 and now
throws a warning by modifying it. If not, then the only way seems to be to
delete the key - if one doesn't want to /allow-weak-digest-algos/ .
Olav
- --
The Enigma
> Is there any way in GPG to change the digest used with an older key?
> I have a SHA-1 digest in a key that I use, and I'd like to make that
> SHA-256 if possible.
DSA-1024 requires a 160-bit hash, so if you're using that you're
(somewhat) out of luck; even if you use SHA256, only 160 bits of it
On 21-3-2015 16:39, Enigmail User wrote:
> On 3/21/2015 06:36, Olav Seyfarth wrote:
> > Hi Patrick,
>
> >> I'm thinking about adding "--allow-weak-digest-algos" to the GnuPG
> >> parameters if GnuPG > 2.0.27 is detected. Would you think this is
> >> a good idea to get rid of the problem -- or this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 3/21/2015 06:36, Olav Seyfarth wrote:
> Hi Patrick,
>
>> I'm thinking about adding "--allow-weak-digest-algos" to the GnuPG
>> parameters if GnuPG > 2.0.27 is detected. Would you think this is
>> a good idea to get rid of the problem -- or this
On 21/03/2015 10:36 am, Olav Seyfarth wrote:
> Hi Patrick,
>
>> I'm thinking about adding "--allow-weak-digest-algos" to the GnuPG
>> parameters if GnuPG > 2.0.27 is detected. Would you think this is a good
>> idea to get rid of the problem -- or this just postponing the problem?
>
> Please don'
On 21/03/2015 9:57 am, Olav Seyfarth wrote:
>
> Hi Bob,
>
>
> Deletion was a shade more complex as two old Thawtes keys had private
> keys, but all is now well. Thanks again,
>
>
> So, how did you solve that? I also had two secret keys, now removed.
> I'd like to restore them, but how to ged rid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Patrick,
> I'm thinking about adding "--allow-weak-digest-algos" to the GnuPG
> parameters if GnuPG > 2.0.27 is detected. Would you think this is a good
> idea to get rid of the problem -- or this just postponing the problem?
Please don't. MD5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.03.15 10:57, Olav Seyfarth wrote:
> Hi Bob,
>
>> Deletion was a shade more complex as two old Thawtes keys had
>> private keys, but all is now well. Thanks again,
>
> So, how did you solve that? I also had two secret keys, now
> removed. I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Bob,
> Deletion was a shade more complex as two old Thawtes keys had private
> keys, but all is now well. Thanks again,
So, how did you solve that? I also had two secret keys, now removed.
I'd like to restore them, but how to ged rid of MD5 ther
On 20/03/2015 10:01 pm, Olav Seyfarth wrote:
installed GnupG 2.0.27, via Gpg4Win 2.2.4
>>> reason is, that GnuPG 2.0.27 errors out if it detects keys using MD5.
>>> Workaround: use allow-weak-digest-algos in Enigmail or gpg.conf
>> Is there a method to search for such keys?
>
> I definitely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi David,
> Googling this suggests it may be a conflict between gnome-agent and the
> gpa-agent. I am running Ubuntu 14.10.
sorry, but this IS off-topic (for this list) now ;-)
But there is some hint on https://www.enigmail.net/support/gnupg2_is
On 03/20/2015 06:01 PM, Olav Seyfarth wrote:
> >>> installed GnupG 2.0.27, via Gpg4Win 2.2.4
> >> reason is, that GnuPG 2.0.27 errors out if it detects keys using MD5.
> >> Workaround: use allow-weak-digest-algos in Enigmail or gpg.conf
> > Is there a method to search for such keys?
>
> I definit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
>>> installed GnupG 2.0.27, via Gpg4Win 2.2.4
>> reason is, that GnuPG 2.0.27 errors out if it detects keys using MD5.
>> Workaround: use allow-weak-digest-algos in Enigmail or gpg.conf
> Is there a method to search for such keys?
I definitely *don
On 03/18/2015 12:04 PM, Bob Henson wrote:
> On 18/03/2015 12:57 pm, Ludwig Hügelschäfer wrote:
>> On 18.03.15 12:11, Bob Henson wrote:
>>> I just installed the new GnupG 2.0.27, via Gpg4Win 2.2.4 vanilla.
>>> I couldnot access the Enigmail key management window at all -
>>> getting the following
On 18/03/2015 12:57 pm, Ludwig Hügelschäfer wrote:
> On 18.03.15 12:11, Bob Henson wrote:
>> I just installed the new GnupG 2.0.27, via Gpg4Win 2.2.4 vanilla.
>> I couldnot access the Enigmail key management window at all -
>> getting the following error message:-
>
>> error The spinner was indica
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18.03.15 12:11, Bob Henson wrote:
> I just installed the new GnupG 2.0.27, via Gpg4Win 2.2.4 vanilla.
> I couldnot access the Enigmail key management window at all -
> getting the following error message:-
>
> error The spinner was indicating tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I confirm issues with Enigmail 1.8 in combination with GPG4win 2.2.4 (full).
I see "gpg: Oops: keyid_from_fingerprint: no pubkey" twice and an error about
key "" being more than once in trustdb along with a hint that MD5 sigs
are rejected wh
On 2015/03/18 20:11, Bob Henson wrote:
> I just installed the new GnupG 2.0.27, via Gpg4Win 2.2.4 vanilla. I
> couldnot access the Enigmail key management window at all - getting the
> following error message:-
>
> error
> The spinner was indicating that it was trying to load the keys, but
> nothi
I just installed the new GnupG 2.0.27, via Gpg4Win 2.2.4 vanilla. I
couldnot access the Enigmail key management window at all - getting the
following error message:-
error
The spinner was indicating that it was trying to load the keys, but
nothing happenedafter a considerable wait.
I reinstalled
22 matches
Mail list logo
