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

Onion Browser needs a more explicit warning about leaks #2929

Closed
2 tasks done
SkewedZeppelin opened this issue Mar 6, 2025 · 2 comments · Fixed by #2934
Closed
2 tasks done

Onion Browser needs a more explicit warning about leaks #2929

SkewedZeppelin opened this issue Mar 6, 2025 · 2 comments · Fixed by #2934
Labels
t:correction content corrections or errors

Comments

@SkewedZeppelin
Copy link
Contributor

SkewedZeppelin commented Mar 6, 2025

Affected page

https://www.privacyguides.org/en/tor/#onion-browser-ios

Description

Current wording is

does not provide the same levels of privacy protections

needs to be adjusted to be more clear about the inherent leaks due to limitations of iOS.

The latest available (3.1.5) also has an issue where data is not cleared on close, although this one will be fixed in the next update (3.2.0). Presumably currently stuck waiting for approval from Apple.

Sources

OnionBrowser/OnionBrowser#509
OnionBrowser/OnionBrowser#508

Before submitting

  • I am reporting something that is verifiably incorrect, not a suggestion or opinion.
  • I agree to the Community Code of Conduct.
@SkewedZeppelin SkewedZeppelin added the t:correction content corrections or errors label Mar 6, 2025
@jonaharagon
Copy link
Member

I will note this, but I see a commit was added regarding this too: OnionBrowser/OnionBrowser@2c69832

@SkewedZeppelin
Copy link
Contributor Author

that commit fixed additional leaks, but those are irrespective of the fundamental leaks mentioned on their faq:

When using the built-in Tor, you will unfortunately leak your real IP address to websites via WebRTC. Also, audio and video streams cannot be tunneled through Tor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:correction content corrections or errors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants