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

Privacy Statements are meaningless when they claim 'no logs' or worse #945

Closed
sambacha opened this issue Feb 16, 2024 · 2 comments
Closed

Comments

@sambacha
Copy link

The problem with that no-logs claim, though, is that you can't prove a negative. Verifying that a service isn't logging user activity is impossible from the outside.

Additionally, just because your service is routed through TOR does not mean it is without downsides: your exit traffic is still controlled by the exit TOR node. This means you can not only be censored, but also fed fake data masquerading as legit RPC traffic. You would never know.

All of these services use some sort of caching middleware, that in itself requires such logging and persisting of user connection information to be able to respond.

@Rjsoon38
Copy link

Thank you so much for the information. I really appreciate that guidance.

@Funinthesun210
Copy link

The problem with that no-logs claim, though, is that you can't prove a negative. Verifying that a service isn't logging user activity is impossible from the outside.

Additionally, just because your service is routed through TOR does not mean it is without downsides: your exit traffic is still controlled by the exit TOR node. This means you can not only be censored, but also fed fake data masquerading as legit RPC traffic. You would never know.

All of these services use some sort of caching middleware, that in itself requires such logging and persisting of user connection information to be able to respond.

Thank you

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

4 participants