Overlapping/conflicting badges? #80
Labels
No labels
new-website
ui
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: data.coop/website#80
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The badges
encrypted_storage
andzero_knowledge
seem to overlap. Forencrypted_storage
, I can't really think of any service where data is encrypted in a way where sysadmins can decrypt the data, so it's essentially just zero-knowledge if data is encrypted (as is the case for Passit and PrivateBin).However, it WOULD be the case if fx. we enabled server-side encryption in Nextcloud, but then the encryption/decryption key is stored on the server as well, so a cyberattack/data breach would leak the key too. Other than that, I can't think of anything where the badge, as it's currently described, applies. We do have plenty of services where
zero_knowledge
applies however.What do you think?
CC: @benjaoming @decibyte @halfd @reynir @valberg
In order to educate and advance knowledge of how services work, I think it's nice to be able to articulate both:
You may be able to use an encrypted service that doesn't fall into the hands of cyber attackers, unless the sysadmins/hardware are also compromised.
You may be able to run an even MORE encrypted service at the cost of being 100% responsible for the encryption yourself.
Does the distinction make sense? I think your example of Nextcloud is good.