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

S.Burmeister sven.burmeister at gmx.net
Thu Feb 1 22:34:18 CET 2007


------- 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         
sven.burmeister gmx net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sven.burmeister gmx net



------- Additional Comments From sven.burmeister gmx net  2007-02-01 22:34 -------
Is it not the way that one even has to trust the key "unconditionally"?

Just trusting or partly trusting it in kgpg is not enough for kmail to allow the user to send an encrypted email to that person. This does not really make sense because then only two states were needed, unconditionally and not trusted.

However, even if I would disagree with the fact that kmail should allow to send emails to untrusted persons, I would expect it to respect the different stati of trust that are possible for a key.

So for sending, it might be sensible to only allow keys > partly trusted, i.e. trusted for sending, but not trusted for receiving.

For receiving I do not know the difference between trusted and unconditionally, yet kmail only displays those emails as trusted that are signed with a key one trusts unconditionally, which is a bug too, IMHO.

To sum up, I think that even if kmail developers really think that it is not justifieable to send emails to untrusted users, there is no reason to not permit this for partially trusted keys.



More information about the pkg-kde-bugs-fwd mailing list