-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9nO/3qCK9CeX6cL8RAt1yAKDnW2UVjTEKmZB899x8zi0/x/uj5ACfVjun CbY6JJJ0p6fuLOAryT8MG2A= =ssD9 -----END PGP SIGNATURE-----
