Hello. Tetsuo Handa wrote: > I created a new key > > pub 4096R/0C64F52A 2013-07-07 [expires: 2018-07-07] > Key fingerprint = 43C8 3369 623D 7AD3 A96C 2FC7 425F 128D 0C64 F52A > uid Tetsuo Handa <pengu****@I-lov*****> > > and added it to http://I-love.SAKURA.ne.jp/kumaneko-key . From now on, I'll > use the new key for signing tarballs and binary packages. Unfortunately, it turned out that older version of RPM cannot handle "4096bit RSA and RSA key" (pitfall described at http://technosorcery.net/blog/2010/10/10/pitfalls-with-rpm-and-gpg/ ). Therefore, I had to create 1024bit DSA key for signing binary packages (because I found this pitfall after purging my old 1024bit DSA key). pub 1024D/FD797347 2013-07-14 [expires: 2018-07-07] Key fingerprint = D932 B37B C4DE C5C2 D88F C8E2 B37F 39F6 FD79 7347 uid Tetsuo Handa (for older versions of RPM which cannot handle 4096bit RSA key) <pengu****@I-lov*****> http://I-love.SAKURA.ne.jp/kumaneko-key was updated to include the new key, but "rpm --import" seems to import only first PGP PUBLIC KEY BLOCK. Ouch! Well, I need to consider updating documentation on how to import my gpg keys. Any good ideas?
TOMOYO
Fork