Fix issues in encrypted chats from profanity to profanity

[paullouisageneau]

Fixes two issues that prevent from sending encrypted messages from profanity to profanity:

• Crash on missing resource in jid (Cannot send encrypted message #39)
• Base64-encoded fields sent with b prefix, causing base64 decoding failure on remote side

[coveralls]

Coverage remained the same at 40.012% when pulling 6e905e8 on paullouisageneau:fix-profanity-to-profanity into a1c77a8 on ReneVolution:master.

[coveralls]

Coverage remained the same at 40.012% when pulling 6e905e8 on paullouisageneau:fix-profanity-to-profanity into a1c77a8 on ReneVolution:master.

[coveralls]

Coverage remained the same at 40.012% when pulling 6e905e8 on paullouisageneau:fix-profanity-to-profanity into a1c77a8 on ReneVolution:master.

[aereaux]

To test this I should just need to check it out and run install.sh (and then /plugins reload), and then it will overwrite the old version of the plugin, right?

[paullouisageneau]

Yes exactly, but you have to specify the plugin name: /plugins reload prof_omemo_plugin.py

[aereaux]

Doesn't /plugins reload without an argument reload all plugins?

[paullouisageneau]

Oh right, it does, good point!

[aereaux]

OK, it looks like this does allow my contacts to successfully receive my messages. I have not yet tested the missing resource in jid part yet. Thanks for the fixes.

[paullouisageneau]

You're welcome! I'm glad it helped.

[ReneVolution]

Thanks @paullouisageneau. It's great to see the community working on this while I can't.
Did you actually test sending messages with special characters like ÖÄÜ or é?

[aereaux]

@ReneVolution Special characters shouldn't matter, right? Because it's just decoding the b64encoded data?

[ReneVolution]

You're right. Merging then.