Existing OMEMO trust model funcionality should be modified #541

Open
opened 9 months ago by andypl · 0 comments
andypl commented 9 months ago

General information

  • Version: 3.0.3-playstore
  • Device: Google Pixel 5
  • Android Version: Android 11 (stock)
  • Server name: -
  • Server software: -
  • Installed server modules: -
  • Pix-Art Messenger source: PlayStore, PlayStore Beta Channel

===== Case one =====

Steps to reproduce case one

  1. Set blind trust to enabled and omemo to enabled for new messages.
  2. Create two account and grant subscription to each other.
  3. Send message from one account to another

Expected result

Message should be encrypted and marked as untrusted, becasue at least one device have blind trust.

Actual result

Messages are encrypted only and user dont ktonw that device

===== Case two =====

Steps to reproduce case two

  1. Set blind trust to enabled and omemo to enabled for new messages.
  2. Create two account and grant subscription to each other.
  3. Login with another new device in first account that support OMEMO
  4. Send message from second account with one device to first account with two device.

Expected result

When second account try to send message to first account Blabber should notify user that new device come out and it will be blindly trusted. Messsage should be send encrypted and marked as not fully trusted. Second and another message should be only marked as not fully trusted as in case one.

When user connect from first device on first account, Blabber should show a notification about own new device, and based on selected trusted model

===== Case third =====

Steps to reproduce third case

  1. Set blind trust to enabled and omemo to enabled for new messages.
  2. Create two account and grant subscription to each other.
  3. Login with another new device in first account that support OMEMO
  4. Send message from second account on first device to second account.

Expected result

When user touch send button, Blabber on first device should show notification that new own device show up and is blidnly trusted. On that notification user should change trust level and send a message.
On another message notification should not be showed and message will be only marked as not trusted for some device if user not change trust level.

===== Case fourth =====

Steps to reproduce fourth case

  1. Set blind trust to disabled and omemo to enabled for new messages.
  2. Create two account and grant subscription to each other.
  3. Login with another new device in first account that support OMEMO
  4. Send message from second account on first device to second account.

Expected result

When user touch send button, Blabber on first device should show a notification to set trusted level for new own device. He can set: not trusted, blind trust or fully trusted.
After set level of trust message should be sended, and marked as not trusted if blind trust is set, or not encrypted to new device is trust level is set to not trusted.

#### General information * **Version:** 3.0.3-playstore * **Device:** Google Pixel 5 * **Android Version:** Android 11 (stock) * **Server name:** - * **Server software:** - * **Installed server modules:** - * **Pix-Art Messenger source:** PlayStore, PlayStore Beta Channel #### ===== Case one ===== #### #### Steps to reproduce case one 1. Set blind trust to enabled and omemo to enabled for new messages. 2. Create two account and grant subscription to each other. 3. Send message from one account to another #### Expected result Message should be encrypted and marked as untrusted, becasue at least one device have blind trust. #### Actual result Messages are encrypted only and user dont ktonw that device #### ===== Case two ===== #### Steps to reproduce case two 1. Set blind trust to enabled and omemo to enabled for new messages. 2. Create two account and grant subscription to each other. 3. Login with another new device in first account that support OMEMO 4. Send message from second account with one device to first account with two device. #### Expected result When second account try to send message to first account Blabber should notify user that new device come out and it will be blindly trusted. Messsage should be send encrypted and marked as not fully trusted. Second and another message should be only marked as not fully trusted as in case one. When user connect from first device on first account, Blabber should show a notification about own new device, and based on selected trusted model #### ===== Case third ===== #### Steps to reproduce third case 1. Set blind trust to enabled and omemo to enabled for new messages. 2. Create two account and grant subscription to each other. 3. Login with another new device in first account that support OMEMO 4. Send message from second account on first device to second account. #### Expected result When user touch send button, Blabber on first device should show notification that new own device show up and is blidnly trusted. On that notification user should change trust level and send a message. On another message notification should not be showed and message will be only marked as not trusted for some device if user not change trust level. #### ===== Case fourth ===== #### #### Steps to reproduce fourth case 1. Set blind trust to disabled and omemo to enabled for new messages. 2. Create two account and grant subscription to each other. 3. Login with another new device in first account that support OMEMO 4. Send message from second account on first device to second account. #### Expected result When user touch send button, Blabber on first device should show a notification to set trusted level for new own device. He can set: not trusted, blind trust or fully trusted. After set level of trust message should be sended, and marked as not trusted if blind trust is set, or not encrypted to new device is trust level is set to not trusted.
andypl changed title from OMEMO Blind trust funcionality is not working as should be to OMEMO Blind trust funcionality is not working as is should be 9 months ago
andypl changed title from OMEMO Blind trust funcionality is not working as is should be to Existing OMEMO trust model funcionality should be modified 9 months ago
kriztan added the
Help wanted
label 8 months ago
Echolon added the
OMEMO/Encryption
label 7 months ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.