Encrypt Channels in a closed Community #12851
Comments
This was referenced Nov 23, 2023
osmaczko
moved this from Iteration Backlog
to In Progress
in Status Desktop/Mobile Board
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 14, 2023
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 14, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. This commit introduces a description encryption for closed communities. The map is pupulated with a single entry. The key is hash ratchet for community-level encryption, and the value is an ecnrypted `CommunityDescription` defining only two fields: `chats` and `members`. As a follow-up, channel-level description encryption will be implemented. Each channel will have its unique entry in the map, with the key being a hash ratchet specific to channel-level encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 15, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. This commit introduces a description encryption for closed communities. The map is pupulated with a single entry. The key is hash ratchet for community-level encryption, and the value is an ecnrypted `CommunityDescription` defining only two fields: `chats` and `members`. As a follow-up, channel-level description encryption will be implemented. Each channel will have its unique entry in the map, with the key being a hash ratchet specific to channel-level encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 15, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. This commit introduces a description encryption for closed communities. The map is pupulated with a single entry. The key is hash ratchet for community-level encryption, and the value is an ecnrypted `CommunityDescription` defining only two fields: `chats` and `members`. As a follow-up, channel-level description encryption will be implemented. Each channel will have its unique entry in the map, with the key being a hash ratchet specific to channel-level encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 21, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852 closes: status-im/status-desktop#12853
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 21, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852 closes: status-im/status-desktop#12853
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 21, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852 closes: status-im/status-desktop#12853
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 22, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852 closes: status-im/status-desktop#12853
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 22, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852 closes: status-im/status-desktop#12853
osmaczko
added a commit
to status-im/status-go
that referenced
this issue
Dec 22, 2023
Extended `CommunityDescription` with a `privateData` map. This map associates each hash ratchet `key_id` and `seq_no` with an encrypted `CommunityDescription`. Each encrypted instance includes only data requiring encryption. closes: status-im/status-desktop#12851 closes: status-im/status-desktop#12852 closes: status-im/status-desktop#12853
github-project-automation
bot
moved this from Code review
to Done
in Status Desktop/Mobile Board
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Closed Communities (communities with a token permission to join) should have the channel list encrypted in the community description.
We can and should reuse the same encryption key that is used to read the messages in the community itself.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: