-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 04 October 2002 2:33 am, bruno randolf wrote: > ok. sorry for my wrong post. i eventually took the time to read the gnu > privacy handbook. what i suggested was nonsense and dangerous. and i'll > never do something like that again, promised... > > what lead me to this stupid workaround was the fact, that kmail 1.4.3 (kde > 3.0.3) refuses to encrypt to keys which are not signed (the old version > allowed this). this behaviour might be right and conforming to the rfcs, > but for casual, uneducated gpg users this is annoying and can lead to such > stupid workarounds. of course it would be best if everybody just read the > manual, but in my case, wouldn't it have been better if i just continued > using the unsigned keys privately? > > anyway, thanks for pointing me to the infos, reading the gpg handbook was > something i always had on my todo list... i'm glad that i've done it now... > > br1
If you really want to be able to encrypt emails to untrusted keys, then you can use --lsign to locally sign the key. You need to check the docs but I beleive that is the correct thing to do. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9nVkYYsCKa6wDNXYRAtEGAKCGce88IMAz4Q0ofuZGyCiK4jP++wCeIozC 2iDdB2IoOKLxUSC7lMY8esA= =olBw -----END PGP SIGNATURE-----
