OleksiiMar 8
hey #xmpp ppl I have a group chat and I end up in the situation where my @dino on #linuxphone doesn't trust to one member and another group member client doesn't trust to my client. We are, a chat members physically far from each other. Could you guide what is the best way to remotely fix it?
Thank you.
Show threadMenel Mar 8
@[email protected]
hi, if you see such a message it is always in the sending client where it can be fixed.

The fix is, you tell them your omemo fingerprint and they make sure that they encrypt for that device.
How to do it depends on the sending client. (is the sender Dino or conversations for example)
@[email protected]
Show threadOleksii
@menel @dino I have both but let's start with Dino
Thank you
Mar 8 at 8:57amWeb
Show threadMenel Mar 8
the sending client. the one that posted the message that can't be read, must be with the open chat window with the contact that can't get the message.
then the three dot menue, "contact details" --> "encryption" tab and be sure that the omemo key there is enabled and the same as your device has (you see your own in your account settings)

CC: @[email protected]
Show threadOleksiiMar 8
@menel @dino Thank you for sharing.
Looks like @dino and #Conversations manage keys quite good, main issue with @Monal
It's more error prone
Show threadOleksiiMar 8

@menel @dino It looks like when ever I login into new device from my account all my contacts getting pop up to trust or not to my new device. Looks like not all accepting it. I guess this is big difference compare to the centralize messengers

update to my group chat issue. Looks like one member / @Monal has fixed automatically.

Show threadmonal-im.org Mar 8

@Oleksii @menel @dino Monal actually does the same as Dino and Conversations: if you never manually trust any device/key, new devices are automatically trusted.

If you manually trusted any key in the past, new devices won't automatically be trusted, because you proved that you want to manually control which devices you trust and which you don't.

If you have a specific scenario in which Monal didn't do exactly this, please share so that I can fix things :)

Show threadOleksiiMar 8
@Monal @menel @dino Great, thank you a lot!
Show threadmonal-im.org Mar 8
@Oleksii @menel @dino the only thing Monal does differently is: it shows a status message in-chat if the remote end added or removed a new device. I could be convinced to not show these if there is no manual trust (as described above) involved for this contact.
Show threadmonal-im.org Mar 8

@Oleksii @menel @dino ah and Monal shows a notification if a new client was added to your own account. Usually that's more actionable because somebody (e.g. you server operator) could try to sneak in a new device to be able to decrypt your conversations.

So you shouldn't ignore that, if it wasn't you logging in on a new device. You can ignore it if you never manually trusted one of your own devices and you should trust this new device if you manually trusted at least one of your own devices.

Show threadOleksiiMar 8
@Monal @menel @dino Ohh, it's really good strategy to know if your account wasn't compromised. For example I think my current server has very weak authentification. I'd to have 2FA or even passkeys option.
Show threadOleksiiMar 8
@Monal @menel @dino I'm wondering what kind of strategy #Conversations_im has? My guess it always asks manually?
Show threadmonal-im.org Mar 8
@Oleksii @menel @dino I think @daniel once told me that it will ask you to trust the new device before sending a message.
Show threadOleksiiMar 8
@Monal @menel @dino @daniel My current group chat issue could confirm this guess :)