Skip to main content
edited body
Source Link
puchu
  • 3.8k
  • 6
  • 44
  • 65

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

Is it possible to protect your website from bots? Generaly speaking yes, but the only good solution is captcha. Do not respect navigator, js env, unique events behaviour, etc. Please don't expect that patches will be fluffy toys like undetected-chromedriver, selenium-stealth, etc.

You should always remember that detection means you want something from unknown application on the client side. Client may remove everything by patching his own application, you don't know how much he (or his employee) knows about web browser and driver source code. You have no chance to detect him if his employee took part in open source web browser development.

Just for example (staffstuff mentioned in this question):

  1. navigator.webdriver
  2. cdc_
  3. HeadlessChrome
  4. Languages
  5. __webdriver

Everything in this list can be hidden/removed in 5 minutes, but there are much more other side effects that can betray the bot.

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

Is it possible to protect your website from bots? Generaly speaking yes, but the only good solution is captcha. Do not respect navigator, js env, unique events behaviour, etc. Please don't expect that patches will be fluffy toys like undetected-chromedriver, selenium-stealth, etc.

You should always remember that detection means you want something from unknown application on the client side. Client may remove everything by patching his own application, you don't know how much he (or his employee) knows about web browser and driver source code. You have no chance to detect him if his employee took part in open source web browser development.

Just for example (staff mentioned in this question):

  1. navigator.webdriver
  2. cdc_
  3. HeadlessChrome
  4. Languages
  5. __webdriver

Everything in this list can be hidden/removed in 5 minutes, but there are much more other side effects that can betray the bot.

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

Is it possible to protect your website from bots? Generaly speaking yes, but the only good solution is captcha. Do not respect navigator, js env, unique events behaviour, etc. Please don't expect that patches will be fluffy toys like undetected-chromedriver, selenium-stealth, etc.

You should always remember that detection means you want something from unknown application on the client side. Client may remove everything by patching his own application, you don't know how much he (or his employee) knows about web browser and driver source code. You have no chance to detect him if his employee took part in open source web browser development.

Just for example (stuff mentioned in this question):

  1. navigator.webdriver
  2. cdc_
  3. HeadlessChrome
  4. Languages
  5. __webdriver

Everything in this list can be hidden/removed in 5 minutes, but there are much more other side effects that can betray the bot.

added 983 characters in body
Source Link
puchu
  • 3.8k
  • 6
  • 44
  • 65

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

Is it possible to protect your website from bots? Generaly speaking yes, but the only possiblegood solution is captcha. Do not respect navigator, js env, unique events behaviour, etc. Please don't expect that patches will be fluffy toys like undetected-chromedriver, selenium-stealth, etc. 

You should always remember that detection means you want something from unknown application on the client side. Client may remove everything by patching his own application, you don't know how much he (or his employee) knows about web browser and driver source code. You have no chance to detect him if his employee took part in open source web browser development.

Just for example (staff mentioned in this question):

  1. navigator.webdriver
  2. cdc_
  3. HeadlessChrome
  4. Languages
  5. __webdriver

Everything in this list can be hidden/removed in 5 minutes, but there are much more other side effects that can betray the bot.

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

Is it possible to protect your website from bots? Generaly speaking yes, but the only possible solution is captcha. Do not respect navigator, js env, unique events behaviour, etc. You should always remember that detection means you want something from unknown application on the client side. Client may remove everything by patching his own application, you don't know how much he (or his employee) knows about web browser and driver source code. You have no chance to detect him if his employee took part in open source web browser development.

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

Is it possible to protect your website from bots? Generaly speaking yes, but the only good solution is captcha. Do not respect navigator, js env, unique events behaviour, etc. Please don't expect that patches will be fluffy toys like undetected-chromedriver, selenium-stealth, etc. 

You should always remember that detection means you want something from unknown application on the client side. Client may remove everything by patching his own application, you don't know how much he (or his employee) knows about web browser and driver source code. You have no chance to detect him if his employee took part in open source web browser development.

Just for example (staff mentioned in this question):

  1. navigator.webdriver
  2. cdc_
  3. HeadlessChrome
  4. Languages
  5. __webdriver

Everything in this list can be hidden/removed in 5 minutes, but there are much more other side effects that can betray the bot.

added 563 characters in body
Source Link
puchu
  • 3.8k
  • 6
  • 44
  • 65

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

Is it possible to protect your website from bots? Generaly speaking yes, but the only possible solution is captcha. Do not respect navigator, js env, unique events behaviour, etc. You should always remember that detection means you want something from unknown application on the client side. Client may remove everything by patching his own application, you don't know how much he (or his employee) knows about web browser and driver source code. You have no chance to detect him if his employee took part in open source web browser development.

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

It is possible to make your web browser and driver invisible. But you need to understand that web browser and driver developers are always under high pressure: headquarters want to be legal, so they accepts special detection mechanisms. So you won't ever receive stealth browser and driver from the box. Solution is the following:

  1. You should patch web browser, driver and selenium itself by removing everything that can be transparent.
  2. Do not share your patches with anyone. If you will publish your patches they will be defeated by new detection mechanism.
  3. You should implement automatic tests that will compare vanilla browser env and patched browser + driver env. It should be identical from any possible point of view. Do not publish your tests.
  4. You should maintain your patches by moving to the next version of web browser, driver and selenium.
  5. You should maintain your tests and update patches when tests fails.

Is it possible to protect your website from bots? Generaly speaking yes, but the only possible solution is captcha. Do not respect navigator, js env, unique events behaviour, etc. You should always remember that detection means you want something from unknown application on the client side. Client may remove everything by patching his own application, you don't know how much he (or his employee) knows about web browser and driver source code. You have no chance to detect him if his employee took part in open source web browser development.

Source Link
puchu
  • 3.8k
  • 6
  • 44
  • 65
Loading