Bug 131345 - GnuPG-Key for contact not for metacontact
Summary: GnuPG-Key for contact not for metacontact
Status: RESOLVED DUPLICATE of bug 138539
Alias: None
Product: kopete
Classification: Applications
Component: Cryptography Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-25 13:58 UTC by Florian Schmid
Modified: 2007-10-20 21:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Schmid 2006-07-25 13:58:21 UTC
Version:           0.12.0 (using KDE 3.5.3, Kubuntu Package 4:3.5.3-0ubuntu0.1 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-26-386

At the moment it`s only possible to assign a GnuPG-Key to a contact. If i use metacontacts all protocols within use this GnuPG-Key. But Encryption doesn`t work for all protocolls (i.e. ICQ, MSN,..).

Would it be possible to assign a GnuPG-Key for each protocoll in a metacontact?

So i perhaps wouldn`t send my girlfriend encrypted SMS ;-)
Comment 1 Charles Connell 2007-10-20 21:31:06 UTC
The crytography plugin has made a design decision that it is better for keys to be associated with metacontacts. One real person has one gpg key, and one metacontact. Also, metacontacts can be associated with KDE address book entries, can hold a gpg key for an entire person. If you don't want to send encrypted SMS's to your girlfriend, turn off encryption temporarily. The KDE 4 version will remember encryption-or-not based on contacts but will remember keys for metacontacts. Also, this is dupe bug.

*** This bug has been marked as a duplicate of 138539 ***