Encrypted Folder = Step Backwards

[12345lamacun]

Hey there,

 

the "new" encrypted Folder-Feature seems to be a neat integration into the overall Concept and UI, at the same time it looks exactly like the Beta-Feature available via API.

 

There were "1.4"-indicators next to Folders using the old "key"/"secret"-based system - which is gone now. Seems to me like you decided to not integrate encrypted folders into the new certificate-based-system and instead just made the old 1.4-feature available to everybody?

 

Are there any disadvantages we need to consider when using this feature, compared to usual certificate-based-folders?

[iswrong]

Are there any disadvantages we need to consider when using this feature, compared to usual certificate-based-folders?

 

The most important difference is that in certificate-based folders, you can change access rights for existing users. With the old secret-based system, once you give e.g. read-write access to a person, you cannot drop it (other than recreating the folder from scratch).

 

Also, with the certificate system all devices associated with an identity are grouped together.

[RomanZ]

@12345lamacun

It is indeed encrypted folder that is now available thru UI for everyone. Please note, that both Advanced folders and Encrypted folders are using cryptography extensively, which costs performance. Mixing Encrypted folders with SSL security behind Advanced folders will make it extremely heavy.

Also, while Advanced folders are designed to be shared with other users, Encrypted folders are more something for a personal use, like a private cloud. And, while using it for yourself there is no need for access management at a cost of performance.

 

The main disadvantage of Encrypted folders is higher CPU load, especially on ARM-based devices.

[12345lamacun]

@iswrong, RomanZ: Thanks for your response! Made it a bit clearer to me ;-)

 

@RomanZ: Will there be a higher CPU-load even if I store the folder encrypted only?

(use case: Storing a folder encrypted-only on a RaspberryPi for redundancy and High-Availability)

 

Thanks!

[iswrong]

4 hours ago, 12345lamacun said:

@RomanZ: Will there be a higher CPU-load even if I store the folder encrypted only?

Yes, because the peers that have read-only or read-write keys now need to encrypt/decrypt twice: once the connection to the encrypted peer, and once to encrypt/decrypt the blocks that that peer receives/sends.