There is a problem in the code:

• xsf/xeps#894

grep OMEMO_AES_GCM_IV_LENGTH

implement a plugin :)

After enabling the OMEMO plugin, all my contacts say "OMEMO is not available for this contact", even though they all have OMEMO-capable clients (Conversations)

There is no button to delete a fingerprint from a contact

Options -> Plugins -> Settings of Stop Spam -> Misc -> View Log

• \ instead of /
• Without Minimize and Maximize buttons

-> https://i.ibb.co/K6tbnx3/psi-stop-spam-plugin-view-log-window.png

Buggy scenario:

1. [UNCONFIRMED] whatever way make a contact untrusted (remove its keys) and likely restart Psi after that.
2. start chatting with the contact using Conversation from the same account like in Psi
3. responses from the remote party will be forwarded (Carbon) to Psi but not shown. while local (sent from local Conversation and forwarded to Psi) messages will be shown on both sides

To workaround this write something to the client from Psi and key confirmation dialog will popup. After that all messages will be shown in Psi.

Expected behaviour:
On receive of forwarded OMEMO encrypted message show notification in events area and on click ask for key confirmation.

Psi: psi-im/psi@ec85e13
plugins: 5dc2190

In conference sometime the OMEMO will be offered and sometimes not. Additional Psi+ don't enter well after restart mainly this (encrypted) conferences!

PS: Thanks for your great job, to integrate OMEMO in the Psi+ (also as Desktop Version available XMPP + OMEMO compatible) software!

The "Mange devices" list only shows device IDs and no fingerprints.

Neither Conversations nor Dino show their device ID - only their fingerprint.
So it is currently impossible to verify the other devices and remove invalid ones.

Hi all!

I downloaded the new version of Psi+, which is based on Psi, and for some reason the HTTP file upload plugin was missing. after some digging I saw that the plugin is now deprecated in Psi.

Is there a reason for that? how are we supposed to 1) send files now? 2) send OMEMO encrypted files?

thanks in advance! :)

Add a new roster contact

[XX:XX:XX] [email protected] Normal message

Not a message, indication for this bug: OMEMO icon is in grey: "OMEMO encryption is not available for this contact"

[XX:XX:XX] Can you send me OMEMO message?
[XX:XX:XX] *** [OMEMO] The following message is from an untrusted device:
[XX:XX:XX] *** Encryption Enabled
[XX:XX:XX] [email protected] OMEMO message test

Not a message, indication for this bug: OMEMO icon is always in grey: "OMEMO encryption is not available for this contact".

[XX:XX:XX] *** [OMEMO] Unable to build any sessions, the message was not sent
[XX:XX:XX] *** Encryption Enabled
[XX:XX:XX] reply 1

Not a message, indication for this bug: OMEMO icon is always in grey: "OMEMO encryption is not available for this contact", and I can not disable forced OMEMO.

[XX:XX:XX] *** [OMEMO] Unable to build any sessions, the message was not sent
[XX:XX:XX] reply 2

Not a message, indication for this bug: OMEMO icon is always in grey: "OMEMO encryption is not available for this contact", and I can not disable forced OMEMO.

Note 1: In Roster, I see "Keys" icon near username of this contact.
Note 2: I have not closed the tab since the first normal message.

Linked to:

• #49
• #54
• #57
• #67
• psi-im/psi#630

I'm trying to compile psi-plus-plugins and I getting an error:

[ 62%] Building CXX object src/plugins/generic/messagefilterplugin/CMakeFiles/messagefilterplugin.dir/messagefilter.cpp.o
In file included from /home/lucjan/Pracownia/Teraz/test/psi-plus-plugins-git/src/psi-plus-snapshots/src/plugins/generic/messagefilterplugin/messagefilter.h:24:0,
                 from /home/lucjan/Pracownia/Teraz/test/psi-plus-plugins-git/src/psi-plus-snapshots/src/plugins/generic/messagefilterplugin/messagefilter.cpp:21:
/home/lucjan/Pracownia/Teraz/test/psi-plus-plugins-git/src/psi-plus-snapshots/src/plugins/generic/messagefilterplugin/options.h:24:10: fatal error: QWidget: No such file or directory
 #include <QWidget>
          ^~~~~~~~~
compilation terminated.
make[2]: *** [src/plugins/generic/messagefilterplugin/CMakeFiles/messagefilterplugin.dir/build.make:74: src/plugins/generic/messagefilterplugin/CMakeFiles/messagefilterplugin.dir/messagefilter.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1888: src/plugins/generic/messagefilterplugin/CMakeFiles/messagefilterplugin.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Commit 2dbc5064 (and older) works fine.

My PKGBUILD:

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=psi-plus-plugins-git

Hello together,

when chatting with OTR enabled with Psi+, those encrypted (and not decrypt-able by anyone else but the receiver [theoretically^^]) messages are forwarded by Prosody to Conversations on my phone (which is the correct behavior of the server since message carbons are enabled). OTR Messages sent by Conversations on the other hand to not get forwarded to any other resource/client. I think I found the reason for it.
When I do not completely misunderstand:
https://xmpp.org/extensions/xep-0364.html
Section: 4.3 Processing Hints
defines a <private ...> stanza to avoid not decrypt-able carbons to be forwarded to other clients. There should be no unexpected and unwanted negative side-effects occur by adding this to OTR encrypted messages, I think.

In case my suggestion is correct I'd really great to see this small but really helpful improvement get implemented.

Thanks for for your work on Psi generally and for any feedback on my feature request above
Cheers!

Some ideas...

so we use webdav to work with the disk.
also we have an API http://api.yandex.ru/disk/
we prefer oauth since we don't want to store user credentials

workflow on plugin enable or on first access to files

1. request access token from yandex http://api.yandex.ru/oauth/doc/dg/reference/obtain-access-token.xml
   • if failed to request token (ex: when client_id is unknown), try to register app
     • say to user we are going to register his Psi(+) on yandex.disk and probaby he has to authorize yourself
     • open webkit window with https://oauth.yandex.ru/client/new
     • check proper page was loading by querying some html elements.
     • if login page or anything else was loaded lets user does what needed.
     • if app registration page was loaded (after authorization probably), autofill all fields and let user to check and agree.
     • get client_id from redirect after submitting form and cache it in settings
   • if failed to request token because client_id is invalid follow steps above to register app
2. as soon as token received we have to store in plugin's settings forever.
3. from this moment the plugin is fully working and may access to webdav files using app token.
4. if yandex.disk starts reporting invalid token go to step 1.

in the user interface we need a field for access token (notice: not client_id) with button receive which executes steps above

Basically having json files with metadata now allow to update their properties dinamicaly on git commit.
So we can a git hook which automatically add entries to the plugins' changelogs.
and then we can make a script which will read recent changlogs, detect if it worth to make new versions relying on the changelog and git history and dump the versions of the changes plugins in their json files.
Also the json file may keep changes for just the latest version.

OMEMO plugin: Options window is little small (7/8 of the fingerprint on one line, last 1/8 on second line)

• https://i.ibb.co/bPzZyhZ/psi-default-window-size-plugins-omemo-problem.png

Better to have only one line.

Since a long time, there is a problem with OTR on Windows x64.

It is impossible to:

• "Generate new key"
• "Start private conversation"

No problem on Windows x86.

version: Psi+ 1.3.398

I have some contacts on im.koderoot.net. I can send and receive unencrypted messages, do an OTR handshake, and receive OTR messages from them, but they cannot receive OTR messages. Psi+ shows it doesn't get a message receipt.

I also tested with Psi 1.3, it doesn't have this problem.

The user on im.koderoot.net uses Pidgin with pidgin-otr plugin.

The servers I tested include xmpp.jp, wehack.space, blug.moe.

Keys icon in Roster near Username is not showed all time.

At each Psi launch, we need to send a message to see it.

OMEMO Encrypted messages to myself do not work (same device/client: Psi or Psi+).

It must be true: "options.ui.contactlist.show.self-contact"

Screenshot: https://i.ibb.co/3yV0ZCy/psi-myself-test-messages-one-with-and-one-without-omemo.png

• Myself Unencrypted message is showed correctly (double and XEP-0184 is perfect): look example "Without" in this screenshot.
• Myself OMEMO message does not work correctly (only one, and no XEP-0184 validation): look example "With" in this screenshot.

EDIT:
I add several examples:

• 1/ Only ONE DEVICE without the own key of current device in "Known Keys" (but it is detected by the client but not added, problem): "*** [OMEMO] Unable to build any sessions, the message was not sent"
• 2/ Only ONE DEVICE with own key of the current device in "Known Keys": "*** [OMEMO] Unable to build any sessions, the message was not sent"
• 3/ Several devices, only one connected (the current device) and the current sent device has not a decrypted OMEMO message in tab "*** OMEMO encryption is enabled"

EXAMPLE 1:
This account has not this own key in "Known Keys" section:

We open the tab:

[XX:XX:21] *** Contact has been switched: [email protected]/Psi+
[XX:XX:21] *** User1 is now Online [1]

XML Console:

<iq id='aac5a' from='[email protected]' to='[email protected]' type='get'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<items node='eu.siacs.conversations.axolotl.devicelist'/>
</pubsub>
</iq>

<iq id="aac5a" type="result" to="[email protected]/Psi+">
<pubsub xmlns="http://jabber.org/protocol/pubsub">
<items node="eu.siacs.conversations.axolotl.devicelist">
<item id="cb76a2f1-4f09-435b-a588-8960d36c35e5">
<list xmlns="eu.siacs.conversations.axolotl">
   <device id="1618399274"/>
  </list>
</item>
</items>
</pubsub>
</iq>

Try to send an OMEMO Message

[XX:XX:46] <User1> ... 
[XX:XX:46] *** [OMEMO] Unable to build any sessions, the message was not sent

XML Console:

<iq id='aac8a' from='[email protected]' to='[email protected]' type='get'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<items node='eu.siacs.conversations.axolotl.bundles:1618399274'/>
</pubsub>
</iq>

<iq id="aac8a" type="result" to="[email protected]/Psi+">
<pubsub xmlns="http://jabber.org/protocol/pubsub">
<items node="eu.siacs.conversations.axolotl.bundles:1618399274">
<item id="79af5a71-faa4-4017-8838-5f6a28cd7171">
<bundle xmlns="eu.siacs.conversations.axolotl">
   <signedPreKeyPublic signedPreKeyId="56810230">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</signedPreKeyPublic>
   <signedPreKeySignature>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</signedPreKeySignature>
   <identityKey>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</identityKey>
   <prekeys>
    <preKeyPublic preKeyId="1">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</preKeyPublic>
    <preKeyPublic preKeyId="100">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</preKeyPublic>
    <preKeyPublic preKeyId="101">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</preKeyPublic>
   </prekeys>
  </bundle>
</item>
</items>
</pubsub>
</iq>

EXAMPLE 2:
This account has this own key in "Known Keys" section, not trusted yet:

We open the tab:

[XX:XX:54] *** Contact has been switched: [email protected]/Psi+
[XX:XX:54] *** User2 is now Online [1]

XML Console:

<iq id='aac6a' from='[email protected]' to='[email protected]' type='get'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<items node='eu.siacs.conversations.axolotl.devicelist'/>
</pubsub>
</iq>

<iq from="[email protected]" id="aac6a" type="result" to="[email protected]/Psi+" xml:lang="en">
<pubsub xmlns="http://jabber.org/protocol/pubsub">
<items node="eu.siacs.conversations.axolotl.devicelist">
<item id="66D3D5DC8BDDA">
<list xmlns="eu.siacs.conversations.axolotl">
   <device id="445276579"/>
  </list>
</item>
</items>
</pubsub>
</iq>

Try to send an OMEMO encrypted message

-> Managing of OMEMO keys dialog window

-> We trust it

[XX:XX:57] *** [OMEMO] Unable to build any sessions, the message was not sent
[XX:XX:57] <User2> ...

XML Console:

NO XML, nothing

EXAMPLE 3:
This account has own key of each device in "Known Keys" section, trusted:

We open the tab:

[XX:XX:20] *** Contact has been switched: [email protected]/Psi+
[XX:XX:20] *** User is now Online [1]

XML Console:

<iq id='aacca' from='[email protected]' to='[email protected]' type='get'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<items node='eu.siacs.conversations.axolotl.devicelist'/>
</pubsub>
</iq>

<iq id="aacca" to="[email protected]/Psi+" xml:lang="en" from="[email protected]" type="result">
<pubsub xmlns="http://jabber.org/protocol/pubsub">
<items node="eu.siacs.conversations.axolotl.devicelist">
<item id="66BE1A3219106">
<list xmlns="eu.siacs.conversations.axolotl">
   <device id="XXXXX"/>
   <device id="XXXXX"/>
   <device id="XXXXX"/>
   <device id="XXXXX"/>
   <device id="XXXXX"/>
   <device id="XXXXX"/>
  </list>
</item>
</items>
</pubsub>
</iq>

Try to send an OMEMO encrypted message

[XX:XX:24] ***  OMEMO encryption is enabled
[XX:XX:24] <User> .... 

-> Only one and no XEP-0184 answer.
The OMEMO message has not been decrypted by this current device.

XML Console:

<message id="aacda" to="[email protected]/Psi+" type="chat">
<active xmlns="http://jabber.org/protocol/chatstates"/>
<request xmlns="urn:xmpp:receipts"/>
<encrypted xmlns="eu.siacs.conversations.axolotl">
<header sid="XXXXXXXXXXX">
<iv>XXXXXXXXXXXXX</iv>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
</header>
<payload>XXXX</payload>
</encrypted>
<store xmlns="urn:xmpp:hints"/>
<encryption xmlns="urn:xmpp:eme:0" namespace="eu.siacs.conversations.axolotl"/>
<body>You received a message encrypted with OMEMO but your client doesn't support OMEMO or its support is currently disabled.</body>
</message>

<message id="aacda" to="[email protected]/Psi+" xml:lang="en" from="[email protected]/Psi+" type="chat">
<archived xmlns="urn:xmpp:mam:tmp" by="[email protected]" id="XXXXXXXXXXXXXXXXXXXX"/>
<stanza-id xmlns="urn:xmpp:sid:0" by="[email protected]" id="XXXXXXXXXXXXXXXXXXXX"/>
<active xmlns="http://jabber.org/protocol/chatstates"/>
<request xmlns="urn:xmpp:receipts"/>
<encrypted xmlns="eu.siacs.conversations.axolotl">
<header sid="XXXXXXXXXXX">
<iv>XXXXXXXXXXXXX</iv>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
<key rid="XXXXX" prekey="true">XXXXXXXXXXXXXXXXXXXXXX</key>
</header>
<payload>XXXX</payload>
</encrypted>
<store xmlns="urn:xmpp:hints"/>
<encryption xmlns="urn:xmpp:eme:0" namespace="eu.siacs.conversations.axolotl"/>
<body>You received a message encrypted with OMEMO but your client doesn't support OMEMO or its support is currently disabled.</body>
</message>

Can you update add the OTRv4 support?

Ping @claucece.

It is impossible to regenerate "Own fingerprint", it is missing

A plugin that adds support for OMEMO encryption.

https://conversations.im/omemo/
https://github.com/omemo

Can you add the XEP-0384: OMEMO Encryption support?

• https://xmpp.org/extensions/xep-0384.html

And XEP-0454: OMEMO Media sharing:

• https://xmpp.org/extensions/xep-0454.html

Diff Tool:

• 0.3.0 to current: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.3.0.html&newfile=https://xmpp.org/extensions/xep-0384.html
• 0.8.3 to current: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.8.3.html&newfile=https://xmpp.org/extensions/xep-0384.html
• 0.8.2 to 0.8.3: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.8.2.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.8.3.html
• 0.8.1 to 0.8.2: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.8.1.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.8.2.html
• 0.8.0 to 0.8.1: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.8.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.8.1.html
• 0.7.0 to 0.8.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.7.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.8.0.html
• 0.6.0 to 0.7.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.6.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.7.0.html
• 0.5.0 to 0.6.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.5.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.6.0.html
• 0.4.0 to 0.5.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.4.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.5.0.html
• 0.3.0 to 0.4.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.3.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.4.0.html

I've faced with very strange problem in psi plus v1.4.554 . When I try to start OTR dialogue with contact who has xabber I always get this kind of message:

?OTR:AAMCkDfq4AAAAAAAAADE7mQeDmVH9oowj+0YW2yHIg9E9mCMRlF7/9Zsgb0e5VodCBZuay9mHkwgWq//yPn7yqs31luqHmcpsUuX6orJha/MdUjpaMfIcg7citqwd+Z7zQpiXvGUqXJpAt2aPVAjGNbb2J45xFVPhwBuTHhZEdG5JW0P4L83u13X/tErSutlUIN30GoZuJeCBYAhrc1HSMMQpciA0mfWPxD8P5weI2W18eTVQF8v78amVYB6LyAzThRs2INtFCw4G8+Skc9zUHKnWAAAACCFNI7bU9ULQfz1YFBZTxNmATGoV23RGT9prV7PrpJ7ng==.

And OTR dialogue doesn't start for sure. I've tryed with different kind of version xabber with the newest 2.6.6.645 and elder one 2.6.2. But with 2.2 it works fine.

Moreover psi+ v0.16 works fine with all kind of version xabber. Dialogues start as usual.

This information below which I get in console when I try to start conversation (contact information has been deleted):

<message to='' type='chat'><subject></subject><body>?OTRv23? ** has requested an Off-the-Record private conversation.  However, you do not have a plugin to support that. If you are using Pidgin in Debian or Ubuntu,install the pidgin-otr package. See https://otr.cypherpunks.ca/ for more information.</body></message>
<r xmlns="urn:xmpp:sm:3"/>

<a xmlns="urn:xmpp:sm:3" h="13"/>

<message to="/Psi+" from="/xabber-android-td36tHn7" xml:lang="en" type="chat" id="kpxrr-3018">
<private xmlns="urn:xmpp:carbons:2"/>
<no-store xmlns="urn:xmpp:hints"/>
<request xmlns="urn:xmpp:receipts"/>
<body>?OTR:AAMC32j9agAAAAAAAADEEP4DvpNiHNjtKKZyOlv1+QkvVwNWWA/z8oG8NRn5bGXVuYHRiz5WCAaH8pniU9uG3ElVUuUoLIP7RDV1u08/xl1uARYzmkPwIx6mQ9xfAFgd9rRgR9Sg+yJzTOzMkT78PY9x7x1Eton6JsnQAquP8Wb7yvmGfqWaTEE7/ZnK9jLRBDIZofdQfXbyZn3f+mbndwWYeyBOeyQUeDYVsuglQ+eEZLzQCG2wwi4+zYv3o1R45i5NvLEYCqElpwBOYuaif56F7gAAACAaFNR/TkA44G9nFRw2BA0VIjJgYrMsT3y/5VD5uPfhZg==.</body>
<thread>ohgJU8w48Rx7</thread>
</message>

Translation in Russian below
Столкнулся с очень странной проблемой в psi plus v1.4.554. При попытки начать ОТР переписку с контактом у которого установлен xabber получаю сообщение вот такого вида:

?OTR:AAMCkDfq4AAAAAAAAADE7mQeDmVH9oowj+0YW2yHIg9E9mCMRlF7/9Zsgb0e5VodCBZuay9mHkwgWq//yPn7yqs31luqHmcpsUuX6orJha/MdUjpaMfIcg7citqwd+Z7zQpiXvGUqXJpAt2aPVAjGNbb2J45xFVPhwBuTHhZEdG5JW0P4L83u13X/tErSutlUIN30GoZuJeCBYAhrc1HSMMQpciA0mfWPxD8P5weI2W18eTVQF8v78amVYB6LyAzThRs2INtFCw4G8+Skc9zUHKnWAAAACCFNI7bU9ULQfz1YFBZTxNmATGoV23RGT9prV7PrpJ7ng==.

Переписка ОТР при этом не начинается. У контакта установлена последняя версия xabber 2.6.6.645 при этом с xabber 2.2 все работает хорошо. В версией xabber 2.6.2 так же не работает.

В psi plus v.0.16 при этом с любой версией xabber все работает нормально и ОТР переписка начинается.

Вот какая информация отображается в консоли при попытки начать ОТР переписку (контакты удалил из логов):

<message to='' type='chat'><subject></subject><body>?OTRv23? ** has requested an Off-the-Record private conversation.  However, you do not have a plugin to support that. If you are using Pidgin in Debian or Ubuntu,install the pidgin-otr package. See https://otr.cypherpunks.ca/ for more information.</body></message>
<r xmlns="urn:xmpp:sm:3"/>

<a xmlns="urn:xmpp:sm:3" h="13"/>

<message to="/Psi+" from="/xabber-android-td36tHn7" xml:lang="en" type="chat" id="kpxrr-3018">
<private xmlns="urn:xmpp:carbons:2"/>
<no-store xmlns="urn:xmpp:hints"/>
<request xmlns="urn:xmpp:receipts"/>
<body>?OTR:AAMC32j9agAAAAAAAADEEP4DvpNiHNjtKKZyOlv1+QkvVwNWWA/z8oG8NRn5bGXVuYHRiz5WCAaH8pniU9uG3ElVUuUoLIP7RDV1u08/xl1uARYzmkPwIx6mQ9xfAFgd9rRgR9Sg+yJzTOzMkT78PY9x7x1Eton6JsnQAquP8Wb7yvmGfqWaTEE7/ZnK9jLRBDIZofdQfXbyZn3f+mbndwWYeyBOeyQUeDYVsuglQ+eEZLzQCG2wwi4+zYv3o1R45i5NvLEYCqElpwBOYuaif56F7gAAACAaFNR/TkA44G9nFRw2BA0VIjJgYrMsT3y/5VD5uPfhZg==.</body>
<thread>ohgJU8w48Rx7</thread>
</message>

Ping @claucece.

Today, I have spoken with a guy for the first time, there was a problem with OMEMO.

I have the Client Switcher plugin and OMEMO plugin enabled:
*** [OMEMO] Unable to build any sessions, the message was not sent

I have disabled the Client Switcher plugin, it is ok, I have enabled a new time the Client Switcher plugin after.

Please note that there is always the big problem of grey OMEMO icon too...

This is for security reasons. It is not safe to pass even public keys in the same communication channel because evil jabber server or evil provider can act like MitM and replace them on the fly for both parties, acting then like client for them all, making valid PGP sessions with both parties with ability to decrypt traffic using its own public keys while sending by stored original public keys.

ldd /usr/lib/psi-plus/plugins/libotrplugin.so
libtidy-0.99.so.0 => not found
local/tidy 5.0.0-2
tidy /usr/lib/libtidy.so
tidy /usr/lib/libtidy.so.5
tidy /usr/lib/libtidy.so.5.0.0

https://aur.archlinux.org/packages/psi-plus-plugins-git/

translateplugin.cpp:92:23: error: «QDomElement» not declared
QString& body, QDomElement& html, bool local);
^
translateplugin.cpp:587:28: error: «QDomElement» not declared
QString &/body/, QDomElement &/html/, bool /local/)

Приветствую всех!
Планируется ли написание плагина "Быстрые сообщения"
Функционал:
в настройках плагина пользователь создаёт набор быстрых сообщений либо как набор строк (т.е. однострочные сообщения), либо как "Заголовок - тело" (в этом случае в теле можно предусмотреть форматирование)
в окне чата создаётся кнопка "быстрый ответ" или "шаблоны" или ещё как-нить...
после нажатия на кнопку в окне чата появляется pop-up меню, и пользователь выбирает сообщение, которое вставится в ... ... ...
в настройках указывается что делать с этим сообщением - либо сразу отправляется собеседнику, либо вставляется в поле ввода сообщения (т.е. пользователь сможет отредактировать текст, и должен будет сам его отправить).

Psi+ version 0.16.556.568-webkit (2016-05-18)
Repeatability: always
Systems: linux (gentoo), windows 8.1
Backtrace obtained in Gentoo Base System release 2.2

Thread 7 (Thread 0x7fffcc638700 (LWP 25079)):
#0 0x00007ffff226c86d in poll () from /lib64/libc.so.6

No symbol table info available.
#1 0x00007fffed66efdc in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#2 0x00007fffed66f10c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#3 0x00007ffff3509feb in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#4 0x00007ffff34ba312 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#5 0x00007ffff330c076 in QThread::exec() () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#6 0x0000000000d60f69 in XMPP::NetTrackerThread::run (this=0x27925b0) at /home/vitaly/github/psi/build/iris/src/irisnet/corelib/netinterface.cpp:168

No locals.
#7 0x00007ffff3310a4a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#8 0x00007ffff14805e6 in start_thread () from /lib64/libpthread.so.0

No symbol table info available.
#9 0x00007ffff2275e2d in clone () from /lib64/libc.so.6

No symbol table info available.

Thread 6 (Thread 0x7fffd77fe700 (LWP 25007)):
#0 0x00007ffff14863af in pthread_cond_wait () from /lib64/libpthread.so.0

No symbol table info available.
#1 0x00007ffff61a3c04 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQt5WebKit.so.5

No symbol table info available.
#2 0x00007ffff61a3c29 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQt5WebKit.so.5

No symbol table info available.
#3 0x00007ffff14805e6 in start_thread () from /lib64/libpthread.so.0

No symbol table info available.
#4 0x00007ffff2275e2d in clone () from /lib64/libc.so.6

No symbol table info available.

Thread 5 (Thread 0x7fffd7fff700 (LWP 25006)):
#0 0x00007ffff226c86d in poll () from /lib64/libc.so.6

No symbol table info available.
#1 0x00007fffed66efdc in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#2 0x00007fffed66f10c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#3 0x00007ffff3509fd4 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#4 0x00007ffff34ba312 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#5 0x00007ffff330c076 in QThread::exec() () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#6 0x00007ffff3310a4a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#7 0x00007ffff14805e6 in start_thread () from /lib64/libpthread.so.0

No symbol table info available.
#8 0x00007ffff2275e2d in clone () from /lib64/libc.so.6

No symbol table info available.

Thread 4 (Thread 0x7fffe524e700 (LWP 24969)):
#0 0x00007ffff226c86d in poll () from /lib64/libc.so.6

No symbol table info available.
#1 0x00007fffed66efdc in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#2 0x00007fffed66f10c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#3 0x00007ffff3509fd4 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#4 0x00007ffff34ba312 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#5 0x00007ffff6b42ca5 in QCA::SyncThread::run() () from /usr/lib64/libqca-qt5.so.2

No symbol table info available.
#6 0x00007ffff3310a4a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#7 0x00007ffff14805e6 in start_thread () from /lib64/libpthread.so.0

No symbol table info available.
#8 0x00007ffff2275e2d in clone () from /lib64/libc.so.6

No symbol table info available.

Thread 3 (Thread 0x7fffe5a4f700 (LWP 24968)):
#0 0x00007ffff226c86d in poll () from /lib64/libc.so.6

No symbol table info available.
#1 0x00007fffed66efdc in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#2 0x00007fffed66f10c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#3 0x00007ffff3509feb in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#4 0x00007ffff34ba312 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#5 0x00007ffff330c076 in QThread::exec() () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#6 0x00007ffff3c2b075 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5

No symbol table info available.
#7 0x00007ffff3310a4a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#8 0x00007ffff14805e6 in start_thread () from /lib64/libpthread.so.0

No symbol table info available.
#9 0x00007ffff2275e2d in clone () from /lib64/libc.so.6

No symbol table info available.

Thread 2 (Thread 0x7fffe687c700 (LWP 24967)):
#0 0x00007ffff226c86d in poll () from /lib64/libc.so.6

No symbol table info available.
#1 0x00007ffff723fb12 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1

No symbol table info available.
#2 0x00007ffff72418f7 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1

No symbol table info available.
#3 0x00007fffe8deea69 in QXcbEventReader::run() () from /usr/lib64/libQt5XcbQpa.so.5

No symbol table info available.
#4 0x00007ffff3310a4a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#5 0x00007ffff14805e6 in start_thread () from /lib64/libpthread.so.0

No symbol table info available.
#6 0x00007ffff2275e2d in clone () from /lib64/libc.so.6

No symbol table info available.

Thread 1 (Thread 0x7ffff7e26780 (LWP 24941)):
#0 0x00007ffff357bba0 in QArrayData::shared_null () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#1 0x00007fffce58f092 in Iconset::reset() () from /home/vitaly/.local/share/psi+/plugins/libscreenshotplugin.so

No symbol table info available.
#2 0x00007fffce58f199 in Controller::~Controller() () from /home/vitaly/.local/share/psi+/plugins/libscreenshotplugin.so

No symbol table info available.
#3 0x00007fffce58f1c9 in Controller::~Controller() () from /home/vitaly/.local/share/psi+/plugins/libscreenshotplugin.so

No symbol table info available.
#4 0x00007fffce56cdbb in ScreenshotPlugin::disable() () from /home/vitaly/.local/share/psi+/plugins/libscreenshotplugin.so

No symbol table info available.
#5 0x00000000009e1fce in PluginHost::disable (this=0x23f0f00) at /home/vitaly/github/psi/build/src/pluginhost.cpp:465

No locals.
#6 0x00000000009e15e5 in PluginHost::unload (this=0x23f0f00) at /home/vitaly/github/psi/build/src/pluginhost.cpp:268

    __PRETTY_FUNCTION__ = "bool PluginHost::unload()"

#7 0x00000000009ebb01 in PluginManager::unloadAllPlugins (this=0x23beae0) at /home/vitaly/github/psi/build/src/pluginmanager.cpp:250

    plugin = 0x23f0f00
    _container_ = {c = {<QListSpecialMethods<PluginHost*>> = {<No data fields>}, {p = {static shared_null = {ref = {atomic = {_q_value = -1}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x2661650}, d = 0x2661650}}, i = {i = 0x2661728}, e = {i = 0x2661760}, control = 1}
    ok = true

#8 0x00000000008478fb in PsiCon::deinit (this=0x1370460) at /home/vitaly/github/psi/build/src/psicon.cpp:753

    acc = {<QListSpecialMethods<UserAccount>> = {<No data fields>}, {p = {static shared_null = {ref = {atomic = {_q_value = -1}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x2594d00}, d = 0x2594d00}}

#9 0x0000000000843823 in PsiCon::~PsiCon (this=0x1370460, __in_chrg=) at /home/vitaly/github/psi/build/src/psicon.cpp:378

No locals.
#10 0x0000000000843a46 in PsiCon::~PsiCon (this=0x1370460, __in_chrg=) at /home/vitaly/github/psi/build/src/psicon.cpp:388

No locals.
#11 0x000000000099c969 in PsiMain::sessionStart (this=0x136a8c0) at /home/vitaly/github/psi/build/src/main.cpp:295

No locals.
#12 0x000000000089d4c8 in PsiMain::qt_static_metacall (_o=0x136a8c0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x136f570) at /home/vitaly/github/psi/build-build-Qt5/src/moc_main.cpp:88

    _t = 0x136a8c0

#13 0x00007ffff34e589a in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#14 0x00007ffff3df641c in QApplicationPrivate::notify_helper(QObject_, QEvent_) () from /usr/lib64/libQt5Widgets.so.5

No symbol table info available.
#15 0x00007ffff3dfaeba in QApplication::notify(QObject_, QEvent_) () from /usr/lib64/libQt5Widgets.so.5

No symbol table info available.
#16 0x0000000000a1c367 in PsiApplication::notify (this=0x7fffffffdec0, receiver=0x136a8c0, event=0x136f200) at /home/vitaly/github/psi/build/src/psiapplication.cpp:398

No locals.
#17 0x00007ffff34bb8a0 in QCoreApplication::notifyInternal2(QObject_, QEvent_) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#18 0x00007ffff34bdc32 in QCoreApplicationPrivate::sendPostedEvents(QObject_, int, QThreadData_) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#19 0x00007ffff3509f53 in postEventSourceDispatch(GSource, int ()(void), void_) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#20 0x00007fffed66ed64 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#21 0x00007fffed66f045 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#22 0x00007fffed66f10c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0

No symbol table info available.
#23 0x00007ffff3509fd4 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#24 0x00007ffff34ba312 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#25 0x00007ffff34c21bc in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5

No symbol table info available.
#26 0x000000000099d8e5 in main (argc=1, argv=0x7fffffffe048) at /home/vitaly/github/psi/build/src/main.cpp:611

    init = {<No data fields>}
    app = {<QApplication> = {<No data fields>}, static staticMetaObject = {d = {superdata = 0x7ffff4305d40 <QApplication::staticMetaObject>, stringdata = 0xdcb740 <qt_meta_stringdata_PsiApplication>, data = 0xdcb840 <qt_meta_data_PsiApplication>, static_metacall = 0x8a7a1e <PsiApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}}
    clIt = {c = {{d = 0x7ffff357cd40 <QHashData::shared_null>, e = 0x7ffff357cd40 <QHashData::shared_null>}}, i = {i = 0x7ffff357cd40 <QHashData::shared_null>}, n = {i = 0x7ffff357cd40 <QHashData::shared_null>}}
    returnValue = 0
    cli = {<SimpleCli> = {<QObject> = {<No data fields>}, argdefs = {d = 0x1325dc0}, aliases = {d = 0x1325e40}}, static staticMetaObject = {d = {superdata = 0x7ffff36f6e80 <QObject::staticMetaObject>, stringdata = 0xdcc1e0 <qt_meta_stringdata_PsiCli>, data = 0xdcc200 <qt_meta_data_PsiCli>, static_metacall = 0x8a8586 <PsiCli::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}}
    cmdline = {{d = 0x7ffff357cd40 <QHashData::shared_null>, e = 0x7ffff357cd40 <QHashData::shared_null>}}
    keystoremgr = <incomplete type>
    cmdlines = {{d = 0x7ffff357cd40 <QHashData::shared_null>, e = 0x7ffff357cd40 <QHashData::shared_null>}}
    psi = 0x136a8c0

We can receive for a contact, an empty fingerprint request, this problem is not new:

• https://i.ibb.co/wgrzN4N/psi-plus-omemo-empty-fingerprint-request.png
• https://i.ibb.co/nfSbjyG/psi-omemo-empty-fingerprint-request-2020.png

А запилите сюда плагин для psto.net https://bitbucket.org/werehuman/psi-psto-plugin/wiki/Home
Работает прекрасно, не глючит...

Minimize/Maximize buttons are missing for:

• Options -> Plugins -> Settings of Client Switcher -> Logs -> View log
• Options -> Plugins -> Settings of Conference Logger -> View Log
• Options -> Plugins -> Settings of Stop Spam -> Misc -> View Log

-> https://i.ibb.co/wWL2pYn/psi-muc-room-history-window-missing-min-max-buttons.png
-> https://i.ibb.co/K6tbnx3/psi-stop-spam-plugin-view-log-window.png

Linked to:

• psi-im/psi#122
• psi-plus/main#642

A contact has not OMEMO (it is specified by the client), the OMEMO icon is in grey and the mouse on it says:

• OMEMO is not available for this contact

When we send a message to a contact, it is forced by OMEMO (not unencrypted message):

• *** [OMEMO] Unable to build any sessions, the message was not sent

There is no possibility to send unencrypted messages in the chat window of the contact, the icon is in grey and disabled.

Right click on our account in roster -> XML Console -> JID -> the [email protected]
-> enable checked

Result for a sent message: Nothing, it is empty.

There is no OMEMO fingerprint for this contact in the client -> Options -> Plugins -> OMEMO plugin -> Fingerprints

Linked to:

• #49
• #54
• #57
• #67
• psi-im/psi#630

files from conversations encrypted with omemo, i can't receive in psi,
files come as url like "aesgcm://.....", please add at least i can recieve...

When we are on a protected MUC Room, after an OMEMO discussion with several people, if we are the last people (alone):

• OMEMO icon: Grey "OMEMO is not available for this contact"

When we send a message:

• *** [OMEMO] Unable to build any sessions, the message was not sent

-> Impossible to disable OMEMO (icon is in grey)

Linked to:

• #49
• #54
• #57
• #67
• psi-im/psi#630

Hello.

I've tried to compile the newest commit and I got an error:

CMake Error at generic/otrplugin/CMakeLists.txt:38 (find_package):
  By not providing "FindLibGcrypt.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "LibGcrypt", but CMake did not find one.

  Could not find a package configuration file provided by "LibGcrypt" with
  any of the following names:

    LibGcryptConfig.cmake
    libgcrypt-config.cmake

  Add the installation prefix of "LibGcrypt" to CMAKE_PREFIX_PATH or set
  "LibGcrypt_DIR" to a directory containing one of the above files.  If
  "LibGcrypt" provides a separate development package or SDK, be sure it has
  been installed.


-- Configuring incomplete, errors occurred!

I've installed libgcrypt:

pacman -Qs libgcrypt && pacman -Fl libgcrypt
local/libgcrypt 1.8.2-1
    General purpose cryptographic library based on the code from GnuPG
local/libgpg-error 1.27-1
    Support library for libgcrypt
libgcrypt usr/
libgcrypt usr/bin/
libgcrypt usr/bin/dumpsexp
libgcrypt usr/bin/hmac256
libgcrypt usr/bin/libgcrypt-config
libgcrypt usr/bin/mpicalc
libgcrypt usr/include/
libgcrypt usr/include/gcrypt.h
libgcrypt usr/lib/
libgcrypt usr/lib/libgcrypt.so
libgcrypt usr/lib/libgcrypt.so.20
libgcrypt usr/lib/libgcrypt.so.20.2.2
libgcrypt usr/share/
libgcrypt usr/share/aclocal/
libgcrypt usr/share/aclocal/libgcrypt.m4
libgcrypt usr/share/info/
libgcrypt usr/share/info/gcrypt.info.gz
libgcrypt usr/share/man/
libgcrypt usr/share/man/man1/
libgcrypt usr/share/man/man1/hmac256.1.gz

Other dep:

pacman -Qs libotr                
local/libotr 4.1.1-1
    Off-the-Record Messaging Library and Toolkit
pacman -Qs libgpg-error
local/libgpg-error 1.27-1
    Support library for libgcrypt
pacman -Qs tidy        
local/tidy 5.4.0-2
    A tool to tidy down your HTML code to a clean style

New OMEMO contact fingerprint request window separate in two lines: 6/8 and 2/8:

• https://i.ibb.co/vYf4kZk/psi-new-omemo-contact-cutted-fingerprint-window-6-on-8-first-line-and-2-on-8-second-line.png

Solution: Increase a little the window size.

?OTR?v2? ... has requested an Off-the-Record private conversation. However, you do not have a plugin to support that. See http://otr.cypherpunks.ca/ for more information.

But I do have the plugin installed and enabled.
local/libotr 4.1.0-1

The XML string is the same as a standard "chat", but is not rendered in GroupChat windows. Only "Image ##### bytes received"

Building in ArchLinux from AUR. Modified PKGBUILD for QT5 support.
Getting error:

g++ -c -pipe -O2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -std=gnu++0x -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_PLUGIN -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. -I.ui -isystem /usr/include/psi-plus/plugins -isystem /usr/include/qt -isystem /usr/include/qt/QtWidgets -isystem /usr/include/qt/QtGui -isystem /usr/include/qt/QtXml -isystem /usr/include/qt/QtCore -I.moc -I.ui -I/usr/lib/qt/mkspecs/linux-g++ -o .obj/attentionplugin.o attentionplugin.cpp

In file included from /usr/include/qt/QtCore/qchar.h:37:0,
from /usr/include/qt/QtCore/qstring.h:41,
from /usr/include/qt/QtCore/qdir.h:37,
from /usr/include/qt/QtWidgets/qfiledialog.h:37,
from /usr/include/qt/QtWidgets/QFileDialog:1,
from attentionplugin.cpp:21:
attentionplugin.cpp:147:1: error: static assertion failed: Old plugin system used
Q_EXPORT_PLUGIN(AttentionPlugin);

^
Makefile:436: recipe for target '.obj/attentionplugin.o' failed

It will be nice to have in "Manage Devices":

• "Clear devices" button for remove (old) not connected XMPP OMEMO clients
• "Refresh" button for have actual list of XMPP OMEMO clients

Have several possibilities of questions/answers (see examples) instead of one question/answer.

Have random questions/answers after it.

Because of a lot of spam messages or spam adding requests.

Examples:

• One question, one answer
• One question, one or more (two+) answers
• Two question, two answers
• ...

It is possible to block adding requests in more simple messages?

When I pressed configuration button for gpg plugin - settings dialog for extended preferences plugin opened:

I'm on latest Psi and Psi+ (psi-im/psi@a3fb596 for Psi and 6ed09da for plugins)

Can you add features?

• End session when logout
• Autoreplay Text on Encrypted Message features

Screenshots:

• https://i.ibb.co/RHk2qvg/psi-plugins-options-otr-current.png
• https://i.ibb.co/QMG9MDk/psi-plugins-options-otr-improvements.png

The Android Conversations xmpp client allows verification of fingerprints by scanning the QR-code on other devices.

It would be nice if psi's omemo plugin would show the QR code of the own fingerprint.

Screenshot of Dino's QR fingerprint popup:

The contents of the QR code seem to be:

"xmpp:" + jid + "?omemo-sid-" + device-id + "=" + fingerprint

for each additional fingerprint, add::

+ ";omemo-sid" + device-id + "=" + fingerprint

Also: omemo/gajim-omemo#146

I seem to have lost the OTR icon that usually appears when I open a new chat window.
I'm using OTR plugin version 1.0.2, latest psi-plus from git, and libotr-4.1.0 in Gentoo.
Everything installed using the rion overlay, as the website recommends.

Anyone know how to debug this?

I have one private MUC with some 15 members where we are using OMEMO. The OMEMO button for that MUC is greyed out however even though I can read OMEMO encrypted messages.

As far as I understood related discussions, Psi expects to have keys of all MUC participants before it allows to send OMEMO encrypted messages? That can be a problem because at least in my MUC some participants are online very sporadically and that will block sending encrypted messages to everybody else in that MUC. Would it be possible to change the implementation to allow sending encrypted messages even though not all recipients would be able to read it?