status-go/protocol/encryption
Pascal Precht f6c9ec7838 refactor: Require request access for all communities
This commit introduces a few changes regarding users accessing
communities:

While the APIs still exist, community invites should no longer be
used, instead communities should merely be "shared".
Sharing a community to users allows users to "join" the community,
which in reality makes them request access to that community.
This means, users have to request access to any community, even if
the community has permissions set to NO_MEMBERSHIP
Only difference between ON_REQUEST and NO_MEMBERSHIP is that
ON_REQUEST communities require manual approval of the owner/admin
to access a community. NO_MEMBERSHIP communities accept
automatically (as soon as owner/admin receives the request).
This also implies that users are no longer optimistically added to the
member list of communities, but only after they have been accepted.

This introduces a bit of a message ping-pong for users to know that
someone is now part of a community
2022-07-08 13:16:12 +02:00
..
github.com/protocol/encryption feat: display name 2022-03-14 13:48:34 -04:00
migrations refactor: Require request access for all communities 2022-07-08 13:16:12 +02:00
multidevice fix: close resultsets so we don't leak them (#1809) 2020-05-14 11:51:32 +01:00
publisher using zap.NewNop() ignores configured log level 2021-08-19 11:35:40 +02:00
sharedsecret Remove unnecessary logs & fix flaky test 2020-11-26 16:25:52 +01:00
README.md Communities encryption 2021-11-30 20:52:47 +02:00
encryption_multi_device_test.go Communities encryption 2021-11-30 20:52:47 +02:00
encryption_test.go Reduce max keep in tests 2022-07-07 13:35:12 +01:00
encryptor.go Communities encryption integration 2022-06-17 21:24:39 +03:00
persistence.go Communities encryption integration 2022-06-17 21:24:39 +03:00
persistence_keys_storage_test.go Move to monorepo structure (#1684) 2019-11-21 17:19:22 +01:00
persistence_test.go Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
protocol.go Communities encryption integration 2022-06-17 21:24:39 +03:00
protocol_message.pb.go refactor: Require request access for all communities 2022-07-08 13:16:12 +02:00
protocol_message.proto Communities encryption integration 2022-06-17 21:24:39 +03:00
protocol_test.go Communities encryption 2021-11-30 20:52:47 +02:00
x3dh.go Create a home submodule for Eth node bridges- Rename StatusBackend to GethStatusBackend 2019-11-27 17:02:09 +01:00
x3dh_test.go Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00

README.md

protocol/encryption package

Hash ratchet encryption

encryptor.GenerateHashRatchetKey() generates a hash ratchet key and stores it in in the DB. There, 2 new tables are created: hash_ratchet_encryption and hash_ratchet_encryption_cache. Each hash ratchet key is uniquely identified by the (groupId, keyId) pair, where keyId is derived from a clock value.

protocol.BuildHashRatchetKeyExchangeMessage builds an 1-on-1 message containing the hash ratchet key, given it's ID.

protocol.BuildHashRatchetMessage builds a hash ratchet message with arbitrary payload, given groupId. It will use the latest hash ratchet key available. encryptor.encryptWithHR encrypts the payload using Hash Ratchet algorithms. Intermediate hashes are stored in hash_ratchet_encryption_cache table.

protocol.HandleMessage uses encryptor.decryptWithHR fn for decryption.