Skip to content

Commit 9e9d22a

Browse files
committed
README tweak
1 parent 3c24204 commit 9e9d22a

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

README.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,7 @@ interface AsyncStorage {
1212

1313
## Why encrypt data in IndexedDB?
1414

15-
> "While the browser can delete IndexedDB files stored on the local filesystem, they can be retrieved by Encase. Unfortunately, the retrieved data is in an unencrypted format, and given the nature of the data held within the IndexedDB API, a potential security issue exists."
16-
> — Stefan Kimak, Jeremy Ellman, Christopher Laing, ["Some Potential Issues with the Security of HTML5 IndexedDB"](https://www.researchgate.net/publication/281066023_Some_Potential_Issues_with_the_Security_of_HTML5_IndexedDB), IET Systems Safety and Cybersecurity Conference 2014.
17-
18-
It is also an issue in the scenario of multiple people sharing the same device and browser.
15+
Encryption keeps data in IndexedDB private, even when a browser profile is shared on the same device. Only one with access to the `cacheKey` can decrypt the data.
1916

2017
## Installation
2118

0 commit comments

Comments
 (0)