As Anytype uses IPFS, which, as far as I’m aware, means the encrypted data is essentially public, which puts an even stronger emphasis on post-quantum cryptography. Even though the encryption is safe today, if it’s easy for someone to get a large number of users’ encrypted data, they could potentially decrypt it in the future and compromise essentially all Anytype users, which is especially important when Anytype markets itself as “for life”.
I’m not very familiar with which algorithms are/aren’t quantum-resistant, and couldn’t find much information on how safe the exact encryption Anytype uses is (“AES with stream encryption with CFB mode”, source). Anytype also doesn’t seem to mention this on their docs/main page.
Does Anytype use post-quantum cryptography? Was this something that was considered, analysed and prioritised? Anytype’s docs mentions it uses a private network. Do nodes use authorisation to prevent someone from downloading all Anytype data, making this attack much less viable?
This isn’t something I’ve thought much about with other services, but it was something I thought of when I heard Anytype uses IPFS due to it potentially being possible to get large amounts of encrypted data without needing to MitM, making it easier for this to be done in the future.
I don’t think it matters. Even if state-of-the-art encryption is used, which is generally the case, there’s no telling it will remain uncracked tomorrow. It is possible the encryption algorithms we use today are all deprecated before quantum computing is employed against encryption. This is one of the reasons why some users want to have the option to keep their data completely offline, only synced between the devices that they own, in Anytype.
I agree with @BGray. I am not an expert on this, but I suppose that this should be considered mostly by cryptographers. It’s just an application of encryption in Anytype. What Anytype can do is to utilize the encryption that is strong enough for now.
But of course, @Orangutan’s concern should be considered seriously, because privacy and security are high priority issues for Anytype in the future.
I agree and that’s something I didn’t consider. Encryption (and security in general) is a moving target and is something that has to be “monitored”, which is something I forgot about at first. I’m sure if the current encryption Anytype uses had a major vulnerability published it would be updated, but I am still interested in Anytype’s quantum safety, as that is a potential “vulnerability” that we do know about and can be worked on in advance. I’m also interested in how easy/hard it would be for a user to obtain a user’s encrypted data (mainly through IPFS) as I think that was the main thing that gave me concerns due to it potentially being easier to get the encrypted data in the first place. For example, what would be the possible ways for a random person to obtain my encrypted data, excluding accessing the unencrypted data on my device/the key stored on my device?
A good rule of thumb. Never put out to the public sphere anything that would cause you significant harm were it to become public in a real sense. Every code can be cracked with sufficient time and resources, with the occasional human error lending a hand. Think of how the enigma code was cracked.