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

update: Note iOS limitations wrt Onion Browser #2934

Merged
merged 1 commit into from
Mar 8, 2025
Merged

update: Note iOS limitations wrt Onion Browser #2934

merged 1 commit into from
Mar 8, 2025

Conversation

jonaharagon
Copy link
Member

List of changes proposed in this PR:

Copy link

github-actions bot commented Mar 8, 2025

Your preview is ready!

Name Link
🔨 Latest commit 885114c
😎 Preview https://pr2934.unreviewed.privacyguides.dev/en/

@SkewedZeppelin
Copy link
Contributor

these are additional separate issues of Orbot, not of the built in Tor feature

@jonaharagon
Copy link
Member Author

I thought it was both. Are there not issues when you use the built-in version?

@SkewedZeppelin
Copy link
Contributor

SkewedZeppelin commented Mar 8, 2025

OnionBrowser can either be used with Orbot or its built in Tor daemon.

Orbot is less likely to leak but Orbot is hinted that it is on its way out due to the memory limitations and can OOM due to iOS restrictions.

OnionBrowser with built-in Tor, which is hinted that it is the future default, will always leak when any audio/video is embedded or WebRTC is used.

@jonaharagon
Copy link
Member Author

Right I see what you mean, we can distinguish between these two cases.

@dngray dngray merged commit f6e2f00 into main Mar 8, 2025
10 checks passed
@dngray dngray deleted the issue-2929 branch March 8, 2025 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Onion Browser needs a more explicit warning about leaks
3 participants