anyproto/docs
1
0
Fork 0
mirror of https://github.com/anyproto/docs.git synced 2025-06-07 21:37:03 +09:00
Code Activity

GITBOOK-444: Small clarification about local encryption

Browse source
This commit is contained in:
Filip Bozicevic 2024-03-04 09:01:18 +00:00 • committed by gitbook-bot
parent 4dec540c7c
commit d43fc95514
No known key found for this signature in database
GPG key ID: 07D2180C7B12D0FF
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
data-and-security/how-we-keep-your-data-safe.md
View file

@ -15,7 +15,7 @@ Due to the nature of Anytype, you're not able to sync your ready-to-edit objects
* These indexes are not synced anywhere and they stay only on your computer. For example, if you have two devices, each of them will have its own index storage
{% hint style="danger" %}
We have a prerequisite that the user’s machine is non-compromised and trusted. Basically, if a device is compromised, there are plenty of attack vectors, including RAM scanning and passphrase keylogging, which is useless. We will definitely make additional encryption later. **For now, we recommend turning HDD encryption and device password on.**
We have a prerequisite that the user’s machine is non-compromised and trusted. Basically, if a device is compromised, there are plenty of attack vectors, including RAM scanning and passphrase keylogging, which makes local encryption much less useful. We will definitely make additional encryption later. **For now, we recommend turning HDD encryption and device password on.**
{% endhint %}
#### Tech details <a href="#tech-details" id="tech-details"></a>