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

Prioritize privacy or security? #14

Open
unixfox opened this issue Jan 15, 2020 · 0 comments
Open

Prioritize privacy or security? #14

unixfox opened this issue Jan 15, 2020 · 0 comments
Labels

Comments

@unixfox
Copy link
Member

unixfox commented Jan 15, 2020

@dalf pushed a commit dalf@37beff9 that fixed the issue #8 but while reviewing the commit I found out that currently searx-stats2 display at a higher priority an instance that have a better Content Security Policy than an instance that doesn't contain any modified scripts (like tracking or ads) so more privacy friendly than an instance with modified scripts.

What should be better for the visitors: prioritize by default the privacy or the security?

Personally I think if #11 gets merged, privacy should be the priority because there are already good mechanisms in modern browsers to secure connections between a client and a server.
Whereas it's more common to have shady scripts built in a Searx instance than having external attackers trying to gather searches from visitors of an instance by injecting scripts into the HTML page.

@dalf dalf added the question label Feb 29, 2020
@mrpaulblack mrpaulblack moved this to Needs Triage in SearXNG Issues May 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Needs Triage
Development

No branches or pull requests

2 participants