mobi/seedvault
1
0
Fork 0
Code Pull requests Activity

document potential information leakage through the long-lived SQL caches

Browse source
This commit is contained in:
Torsten Grote 2021-09-02 14:18:41 +02:00 committed by Chirayu Desai
parent 012bdefb6b
commit 308e7148aa
1 changed files with 12 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
storage/doc/design.md
View file

@ -244,11 +244,21 @@ The derived seed key (512 bit size) gets split into two parts:
## Local caches ## Local caches
The local cache is implemented as a sqlite-based Room database
which had shown promising performance in early tests.
Most information in the cache is considered public knowledge
also available to an attacker with access to the local filesystem
(with root access or file management permission).
Still, the cache data can only be accessed by the owning backup application
and can not be accessed by other apps unless the attacker obtains root access
or is otherwise able to break Android's security model.
In that later case, the attacker will be able to access all files anyway
making access to the cache worthless.
### Files cache ### Files cache
This cache is needed to quickly look up if a file has changed and if we have all of its chunks. This cache is needed to quickly look up if a file has changed and if we have all of its chunks.
It is implemented as a sqlite-based Room database
which had shown promising performance in early tests.
Contents: Contents: