-
Notifications
You must be signed in to change notification settings - Fork 3
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
[FF#1499592] Leaks at least 1 outbound request to any attacker #5
Comments
Disturbingly, TODO: try |
Alas. So, it looks like we can't make a properly-failsafe constrainer with just the APIs given us. The best we can do (for now) is "throwing the breaker" after 1 full bad connection has already been made. Perhaps, once the rest of the functionality's implemented, Mozilla would hear out our requests for better access. |
|
a mitigation, for an attacker who isn't aware of this add-on: hook |
Consider an attacker who is aware of this Add-on.
They might:
remember that in The Internet, you have other, aggressive intelligences finding ways your software diverges from what you thought you wrote… everything doesn't go "as planned"; you've got to be airtight or its utility is only marginal
The text was updated successfully, but these errors were encountered: