5d0ff961b2
crypto: Check the Olm message hash if we fail to decrypt an Olm message.
...
Wether by accident (the next_batch token doesn't get stored properly) or
by malicious intent (the server replays a message) an Olm encrypted to-device
message may appear multiple times.
This is usually fine since nothing bad happens, we don't decrypt the message
and the message gets thrown away.
Since the introduction of Olm session unwedging an undecryptable message
leads to the creation of a new fresh Olm session. To avoid this we
remember which Olm messages we already decrypted so they don't trigger
an unwedging dance.
2020-12-01 14:50:04 +01:00
270350cd34
crypto: Save the olm message hash.
2020-12-01 14:38:03 +01:00
ae2391791d
crypto: Use a released sqlx version.
2020-12-01 13:25:51 +01:00
24592adbba
crypto: Return a higher level struct when decrypting olm messages instead of tuples
2020-12-01 12:41:11 +01:00
efe659910f
crypto: Remove some stale TODOs.
2020-12-01 11:20:55 +01:00
08babb6d6c
crypto: Document the new cross signing methods in the store.
2020-12-01 10:54:41 +01:00
7e9baf2707
crypto: Remove some dead code definitions.
2020-11-26 14:15:52 +01:00
3073883076
crypto: Fix a clippy warning.
2020-11-26 14:02:35 +01:00
7ec5a5ad1a
Merge branch 'master' into crypto-improvements
2020-11-26 13:24:57 +01:00
0422bae924
Fix clippy lint rc_buffer
2020-11-25 19:01:28 +01:00
dedb1eb745
Merge branch 'update-ruma'
2020-11-20 21:21:24 +01:00
c40edcf2fc
matrix-sdk: Try to lower our compile times, at least in the crypto part for now.
2020-11-20 20:35:48 +01:00
95243003c4
Update ruma
2020-11-20 20:14:18 +01:00
b27f1b0e34
crypto: Fix some clippy warnings.
2020-10-30 14:38:29 +01:00
b67cd4ddd2
crypto: Create a trusted public cross signing identity when we create a private one.
2020-10-30 13:21:14 +01:00
44cc1cef71
crypto: Let devices hold on to the private identity.
2020-10-30 11:41:48 +01:00
34bec59389
crypto: Hold on to the private identity in the store.
2020-10-30 11:34:55 +01:00
cb95f576a5
crypto: Clear out the signatures when signing a device.
...
This avoids re-uploading all the existing signatures.
2020-10-29 15:37:29 +01:00
5c530cf9ee
crypto: Upload signatures after verification is done.
2020-10-27 16:39:23 +01:00
30a78bb1d6
crypto: Add the private identity to the Sas object.
2020-10-27 14:21:22 +01:00
2077ea0ddf
crypto: Split out the device_key signing method.
2020-10-27 13:48:51 +01:00
e757d605f5
crypto: Allow users to be signed as well.
2020-10-27 13:29:19 +01:00
61a5293af5
cyrpto: Document the signing module.
2020-10-26 16:03:59 +01:00
6e83a4bbca
crypto: Split out the signing module into two files.
2020-10-26 16:03:59 +01:00
5c14910126
crypto: WIP cross signing bootstrap.
2020-10-26 16:03:59 +01:00
8ed1e37cef
crypto: Save the account if we create a new one.
2020-10-23 11:17:37 +02:00
5fd004bae5
crypto: Connect the private identity to the verification machine.
2020-10-23 11:17:13 +02:00
7de002b128
crypto: Fix some lint issues.
2020-10-22 16:40:05 +02:00
f60dc7ed78
crypto: Allow cross signing identities to be stored/restored.
2020-10-22 16:25:25 +02:00
78d7f6c10b
crypto: Fix a clippy issue.
2020-10-21 17:05:36 +02:00
fa25ca4475
crypto: Make the pickle key encryption future proof.
2020-10-21 16:52:40 +02:00
c9db63509f
crypto: Add error handling to the signing module.
2020-10-21 16:24:10 +02:00
ac0df5dea9
crypto: Properly handle errors in the pickle key decryption.
2020-10-21 15:28:43 +02:00
d175c47a05
crypto: Use a random pickle key in the sqlite store.
2020-10-21 15:13:21 +02:00
959e8450af
crypto: Use a transaction to create sqlite tables.
2020-10-21 14:01:27 +02:00
dd0642cd59
crypto: Add a pickle key struct.
2020-10-21 13:21:22 +02:00
6a7da5a8b6
crypto: Correctly generate a random nonce for pickling of the signing objects.
2020-10-21 12:55:45 +02:00
7cab7cadc9
crypto: Rework the cryptostore.
...
This modifies the cryptostore and storage logic in two ways:
* The cryptostore trait has only one main save method.
* The receive_sync method tries to save all the objects in one
`save_changes()` call.
This means that all the changes a sync makes get commited to the store
in one transaction, leaving us in a consistent state.
This also means that we can pass the Changes struct the receive sync
method collects to our caller if the caller wishes to store the room
state and crypto state changes in a single transaction.
2020-10-20 17:19:37 +02:00
728d80ed06
crypto: Connect the cross signing to the main state machine.
2020-10-19 16:03:01 +02:00
404cc410cc
crypto: Fix the docs and return value of the import_keys method.
2020-10-17 14:39:19 +02:00
93f49265a6
crypto: Use a git version of sqlx.
...
The beta release has a nasty bug where one thread would consume 100% of
CPU.
2020-10-16 19:42:41 +02:00
425a07d670
crypto: Don't load all the devices in the sqlite store.
2020-10-16 16:57:26 +02:00
4262f1d3b0
crypto: Don't cache inbound group sessions in the sqlite store.
2020-10-16 15:54:50 +02:00
b5560d3cb6
crypto: More transactions in the sqlite store.
2020-10-16 15:23:34 +02:00
fc54c63a4c
crypto: Upgrade sqlx to the beta release.
...
This change is much needed to enable transactions in our sqlite store,
before this release creating a transaction would take ownership of the
connection, now it just mutably borrows it.
2020-10-16 15:05:53 +02:00
e7a24d5e68
crypto: Move the session managers under a common module.
2020-10-16 11:09:55 +02:00
b5c9473424
crypto: Test the session unwedging logic.
2020-10-15 15:03:22 +02:00
59d7b53242
crypto: Add an user for a key request if the device was marked as wedged.
2020-10-15 15:02:02 +02:00
59a7199202
crypto: Initial test for the session manager.
2020-10-15 13:58:35 +02:00
d1313b8614
crypto: Fix another clippy warning.
2020-10-14 16:15:26 +02:00
Damir Jelić
Jonas Platte
Alejandro Domínguez