Alphax <[EMAIL PROTECTED]> writes: >> gpg: [EMAIL PROTECTED]: skipped: unusable public key >> gpg: [stdin]: encryption failed: unusable public key >> [EMAIL PROTECTED]:~/src/gnupg$ gpg -a -e -r [EMAIL PROTECTED] >> gpg: 1643B926: There is no assurance this key belongs to the named user >> >> pub 2048g/1643B926 2002-01-28 David M. Shaw <[EMAIL PROTECTED]> >> Primary key fingerprint: 7D92 FD31 3AB6 F373 4CC5 9CA1 DB69 8D71 9924 2560 >> Subkey fingerprint: F0EC 51D9 2ED0 C183 8977 DDD0 AE28 27D1 1643 B926 >> >> It is NOT certain that the key belongs to the person named >> in the user ID. If you *really* know what you are doing, >> you may answer the next question with yes. >> >> Use this key anyway? (y/N) >> > > Have you tried it with > > trust-model always > > in your gpg.conf? The key you're trying to encyrpt to probably isn't > within your trust path.
No, that only removes the question on the second invocation of gpg. It doesn't make the first one succeed. The key appear to be found and imported successfully, but gpg doesn't seem to be able to use it immediately. >> Btw, DNS CERT retrieval work fine, see: > > Oh yes, congrats on RFC 4398. Thanks! _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
