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

Hijacking address bar search engine in Chrome #90

Closed
codebudo opened this issue Jan 24, 2018 · 8 comments
Closed

Hijacking address bar search engine in Chrome #90

codebudo opened this issue Jan 24, 2018 · 8 comments
Assignees
Labels
needs response issue that needs a response from the product team

Comments

@codebudo
Copy link

The primary complaint about this extension on the Chrome webstore 'reviews' seems to be related to this extension forcing the user to use DDG as the default search engine in the address bar. The other feature (privacy protection, letter grading for privacy, blocking, etc.) seem to be most welcome, so these two features should be disentangled.

I received a popup asking if I would like to restore my previous search setting, but after clicking 'no' I'm no longer able to restore my previous default search settings through the extension 'options' without disabling it entirely.

Either:

  1. Don't alter the default address bar search settings, or
  2. Allow the user to restore their previous setting (either through the extension 'options' or the standard Chrome settings).
@alohaas alohaas added the needs response issue that needs a response from the product team label Mar 2, 2018
@s-rd
Copy link

s-rd commented Mar 16, 2018

I'd also like an answer to this. I like the tracker blocker, letter grading, etc., but I often need the other search engines as well in other situations.

Would be nice to be able to configure this myself, preferably like one of @codebudo's proposals.

@willemavjc
Copy link

willemavjc commented Jun 18, 2020

Two years later, this main complaint still remain. I'm personally uninstalling it for this very reason though I jumped out of joyce discovering a privacy enforcement extension from DuckDuckGo at first.

The search engine should definitely not being altered so that the default address bar search settings should remain after installing this extension; or at least, some kind of pop-up dialog should ask for a change. That would be the least.

The actual behavior is no different from Google, the very one criticized everywhere. This even gives a feeling of some personal war against them, as we all know it is the main challenger. People should remain free to choose whatever the search engine, even if this is one creepy.

Right now, you're mixing two different things:

  • An extension about privacy
  • A fight for a market share through search engines

@alohaas and @russellholt : Could you please explain/detail the true/hidden/whatever reasons behind this? This may lead to a true debate in fine.

@willemavjc
Copy link

willemavjc commented Jun 18, 2020

To anyone interested: I managed to bypass the DuckDuckGo search engine.

Seems related to the issue #140 leading to a mandatory override of Chrome (or Chrome-like) settings.

How to do it:

  1. Uninstall DuckDuckGo Privacy extension
  2. Download the DuckDuckGo Privacy extension but cancel the installation process to keep the CRX file which behaves like a ZIP
  3. Unzip the CRX file (e.g. with 7-Zip)
  4. Open the new folder
  5. Get rid of the folder _metadata
  6. Edit the file named manifest.json
  7. Replace the Chrome settings overrides data (line 28 as of 2020/6)
  8. Go to Chrome/Chrome-like extensions manager (e.g. edge://extensions/)
  9. Activate the Developer mode option
  10. Click on Load unpacked
  11. Select your uncompressed folder in step 3
  12. Confirm
  13. The End

Example of Chrome settings to get back to Google (Encrypted):

  "chrome_settings_overrides": {
    "search_provider": {
      "encoding": "UTF-8",
      "favicon_url": "https://encrypted.google.com/favicon.ico",
      "is_default": true,
      "keyword": "google.com",
      "name": "Google",
      "prepopulated_id": 92,
      "search_url": "https://encrypted.google.com/search?q={searchTerms}",
      "suggest_url": "https://encrypted.google.com/complete/search?q={searchTerms}"
    }
  },

@jonathanKingston
Copy link
Collaborator

See also: @sammacbeth's response #492 (comment) where we can't fix this.

This is a Chrome limitation - if we want to change the default search engine on install we have to set this is_default flag. However, once we set this Chrome will lock the search engine choice.

There are a couple of workarounds if you want to keep the extension's privacy protections but not use our search all the time:

1. Use our `!` bangs to redirect to different search engines when you need them

2. Install _another_ extension that changes the default search engine, which will then unlock your search setting in Chrome.

@unuing
Copy link

unuing commented Oct 1, 2022

Since there is a limitation, why do you still persist in setting the search engine?

@tachibana-shin
Copy link

I don't know. I thought duckduckgo would never fix this, so I created this repository fork. download the zip file from the release in my repo it won't lock your search

https://github.com/tachibana-shin/duckduckgo-privacy-extension

@unuing
Copy link

unuing commented Oct 28, 2022

I suggest that you can show a webpage which tell the user to use ddg search engine when installing the extension, instead of force the user to use ddg.

@sammacbeth
Copy link
Collaborator

One of the primary purposes of this extension is to provide an easy, one-click way to switch search engine to DuckDuckGo. Doing what you suggest will make it more difficult for users to switch.

We plan to discuss with Chrome how they could improve the browser settings around search extensions, and thus fix this issue on their end.

@sammacbeth sammacbeth closed this as not planned Won't fix, can't repro, duplicate, stale Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs response issue that needs a response from the product team
Projects
None yet
Development

No branches or pull requests

9 participants