I can see that :P
But do you know how I can fix it?
FYI my new key is signed by the expired key too.
I will sign any new key (without issues) using my old key too.
Washington Sanchez:
> Dude, things are looking pretty suspicious. You drop off the radar, along
> with caedes AFAIK, and suddenly change your PGP key (which has issues).
>
> Let me know I'm crazy and being over cautious here.
> On 5 May 2015 11:11 pm, "Amir Taaki" <genjix@???> wrote:
>
>> Hey, thanks for pointing this out. Do you know how to fix it? I tried
>> searching on the net but found nothing.
>> There's nothing mentioning MD5 in my .gnupg/gpg.conf file.
>>
>> Pablo Costa:
>>> On 05/04/2015 10:48 AM, Amir Taaki wrote:
>>>> This new key has been signed by my old key.
>>>
>>> Hello Amir, I am attaching a warning issued by my gnupg about your
>>> public key. Just so you know, if you didn't:
>>>
>>> $ gpg --import genjix.pgp.asc
>>> gpg: key 32F93378: public key "Amir Taaki <genjix@???>" imported
>>> gpg: Total number processed: 1
>>> gpg: imported: 1 (RSA: 1)
>>> gpg: WARNING: digest algorithm MD5 is deprecated
>>> gpg: please see https://gnupg.org/faq/weak-digest-algos.html for more
>>> information
>>>
>>> I am attaching my public keys also. Maybe you'll see the same warning
>>> when importing them :) It's quite possible. xD
>>>
>>> Take care,
>>> pablo
>>>
>> _______________________________________________
>> unSYSTEM mailing list: http://unsystem.net
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/unsystem
>>
>
>
>
> _______________________________________________
> unSYSTEM mailing list: http://unsystem.net
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/unsystem
>