Bug 120556 - Kopete to find out wether to use PGP or not
Summary: Kopete to find out wether to use PGP or not
Status: RESOLVED INTENTIONAL
Alias: None
Product: kopete
Classification: Unmaintained
Component: Cryptography Plugin (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-21 15:30 UTC by Pupeno
Modified: 2007-10-20 21:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pupeno 2006-01-21 15:30:33 UTC
Version:            (using KDE KDE 3.5.1KDE 3.4.3KDE 3.4.3)
Installed from:    Ubuntu PackagesUbuntu PackagesUbuntu Packages
OS:                Linux

It would be nice if Kopete was able to find out whether to use PGP or not based on the capabilities of the other end.
I use PGP and my wife's uses it as well, we normally communicate using kopete and jabber, all encrypted.
Everything is OK until I am roaming where I don't have my key (and I don't want to put my key on a untrusted computer). There the problem arise, because I still get encrypted messages that I can decrypt.
It would be nice if Kopete could somehow find out when the other side wasn't unable to de-crypt and show a message about this situation offering to switch to a more insecure situation.
I don't know if that can be implemented, if not, a simpler feature would be that Kopete offers to stop sending encrypted information when the other side sends unencrypted information (after all, when one side is encrypted, it is likely that both are); popping up a dialog offering to not send encrypted data for this session, for ever, to send it encrypted for this session or forever.
Thank you.
Comment 1 S. Burmeister 2007-01-16 08:21:19 UTC
For Jabber there is XEP-0116 which describes how two clients can negotiate whether to use encryption or not.

http://www.xmpp.org/extensions/xep-0116.html
Comment 2 Charles Connell 2007-10-20 21:47:09 UTC
The current crypto architecture does not allow this sort of client-to-client negotiation. Jabber has support for encryption, but the cryptography plugin does not plan to use this. The plugin is protocol-independent and operates on a per-message basis. Messages are simply transformed from plaintext into OpenPGP text blocks. There is no protocol-level communication at all. If the Jabber protocol plugin wants to support crypto separately from the cryptography plugin, that is another issue.