[Bug 44699] can't encrypt with gpg if the receiver's key is not signed

[Jon-Pierre Gentil]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
You are a voter for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=44699         




------- Additional Comments From jgentil sebistar net  2007-02-01 21:40 -------
Sometimes I don't care about the identity, I want to encrypt to someone I don't trust.  Sometimes even if I don't trust the key, I still wish to have something encrypted to the recipient, even if I don't fully trust them.

I think more to the point is that KMail should not dictate how I wish to use GPG.  That's GPG's job.  If GPG suddenly implements a feature to disallow this behaviour, then that is where the choice should be made.  Until then, it is considered a feature of GPG to allow encryption to an untrusted key.  Thus, KMail should support as many features of GPG as possible, including encryption to an untrusted key.  The importance of this is freedom of choice.  KDE is a plethora of options.  You open up the Control Center, and you can customize so many different levels of features.  Yet in this one single regard, the KDE development team suddenly chooses to restrict a feature (that seems incredibly easy to change) rather than allow the freedom, which in my opinion, breaks the spirit of KDE.