Bug 175091

Summary: unencrypted message sent with "encryption+signing" enabled
Product: [Unmaintained] kopete Reporter: AlfonsName
Component: Jabber PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: charles, finex, pali.rohar
Priority: NOR    
Version First Reported In: 0.60.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 4.11
Sentry Crash Report:

Description AlfonsName 2008-11-14 00:24:42 UTC 
Version:           0.60.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

* Installed a ubuntu intrepid on x86.
* I loaded the openpgp encryption plugin.
* I created a jabber account for kopete
  and a jabber account for pidgin.
* I selected both an gnupg account to sign the messages
  and a public key for the receiving entity (both in kopete).
* I'm using kopete to send messages and pidgin -d to
  receive messages.

* Sending plain text messages works. 
* Sending encrypted messages works. (jabber:x:encrypted is received)
* Sending signed messages does not work: no error is given
  but there is no <x xmlns="jabber:x:signed"...>...</x> node
  in the received message. (nor anything else looking like a signature)
* Sending encrypted+signed messages results in
  receiving plain text messages.

I enabled/disabled signing/encryption using the buttons with icons in the utilities bar.
Comment 1 AlfonsName 2008-11-14 00:27:24 UTC 
Both accounts are registered on jabber.ccc.de .
Comment 2 Charles Connell 2008-11-17 23:41:28 UTC 
Upon inspection, it appears that Kopete's Jabber plugin is messing with the messages after they have been processed by the cryptography plugin. This is a good thing, but it needs to be updated to reflect the fact that messages can now be signed and/or encrypted.
Comment 3 Pali Rohár 2013-06-04 18:02:25 UTC 
This should be fixed in last kopete and cryptography plugin from svn.