Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better terminology to describe server posture #44

Open
rocodes opened this issue May 9, 2024 · 0 comments
Open

Better terminology to describe server posture #44

rocodes opened this issue May 9, 2024 · 0 comments

Comments

@rocodes
Copy link
Contributor

rocodes commented May 9, 2024

From mastodon:

I'm somewhat perplexed by the new SecureDrop protocol - https://securedrop.org/news/introducing-securedrop-protocol/

Specifically: "The server is “untrusted” in the sense [it] learn[s] nothing about users & messages besides what is inherently observable from its pattern of requests, and it should not have access to sensitive metadata, or sender or receiver information"

Seems like a very weak definition of "untrusted", especially when two comparison techniques explicitly attempt to restrict knowledge derived from access patterns.

This is a valid critique - our intention is to find terminology for "a server that has little-enough information about its users that it could conceivably be deployed in an adversarial environment, eg where disk/RAM snapshots could occur," but maybe we need to work on how we define that, since the server is still a privileged asset and has access to more information than a generic internet user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant