Antonio Diaz Diaz <[email protected]> writes: > Hi Sam,
Hi Antonio, > > Sam James wrote: >> This key (1E5AEE0B18C0DEB45D64AA0325B62C9821501AA0) is different from >> the one you usually use for releases >> (1D41C14B272A2219A739FA4F8FE99503132D7742). > > Yes. I had to generate a new key because the old 1024-bit DSA key was > no longer accepted by Debian. Ah, of course. > >> Would you be able to sign the old key with the new key, and vice-versa? > > Of course. > > I think I have done it, but I'm having trouble uploading the key block > to Savannah. Savannah says it could import both keys, but when I click > on 'Download GPG Key' it sends me the old key alone. To allow you > check the keys while I find out what the problem is, I send you in > another message the output of > gpg --armor --export 8FE99503132D7742 25B62C9821501AA0 Thank you very much! Received and everything is indeed well too. > > (I think this is the second time in 23 years that I have needed to use > gpg for anything other than signing or verifying tarballs). Let's say it's a credit to the tool ;) > > Best regards, > Antonio. Thanks again. I appreciate you doing this. sam
signature.asc
Description: PGP signature
