-
Notifications
You must be signed in to change notification settings - Fork 118
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
Cookie Sync in Burst #414
Comments
@antonsoroko I've tested this solution with few trackers that were not working on my test host, both are working now. I guess we will need to verify the ones protected by Cloudflare. And also check with Python2 Kodi, I was not able yet to make a proper testing. I was not yet releasing new version, as I think there might be issues and it needs a proper testing first. |
This functionality was released with Burst 0.0.87 and can be used. Cookie sync would not work with Kodi 17 and earlier, as the Cryprography module, required for decrypting cookies is not available there. Also, as mentioned in #240 , Cookie sync addon does not store browser UserAgent, that was used while creating cookies. Also it does not store TLS fingerprints of the device that we run. I don't think current addon maintainer would do those changes, and without them we need to make sure Burst is using same UserAgent as the browser. |
@elgatito what about public trackers like 1337 and torrentgalaxy? it there a way to use this to bypass cloudflare for public trackers? i mean, it is possible to login to some public trackers but some trackers might be purely anonymous. and anyway, i guess in general people usually do not have logins for public trackers. |
In Burst we have (for long time) commong cookie jar (not separate per-provider, as it was before). So if you sync cookies for a public tracker - they will be synced as well ( |
@antonsoroko You can install addon to Chrome and run it without password to have cookies unencrypted, to see how contents of that Gist looks like. |
otherwise people will not understand what to do and how to use this feature.
it does not allow me to save settings w/o password. looks like it is intended: https://github.com/Andiedie/sync-my-cookie/blob/6357c0d3a8a09e999c31f00c6bfc3c54d2d0cb43/src/components/setting/setting.tsx#L84 |
did some testing: torrentgalaxy (own protection) - previously it was giving me captcha page in burst debug log, with "cookie sync" - ok cloudflare: (tried even with/without my own "user agent" - same result) other providers do not give me "Just a moment" page, so can't say anything about them. |
Description
Currently there are websites that are protected by captchas or Cloudflare to block robots.
While there are ways to bypass it using browser emulators (like Jakett, etc), it can be not available for all the platforms.
As an alternative approach we now have a code in Burst that can use cookies, synced from other devices, that run Chrome.
Burst will get cookies into HTTP client and use them for doing requests.
In case
providers.json
is having configuration, that describes session cookie for specific provider - Burst will try to skip authentication and consider ourselves as logged in (so no login/password required in this case to be filled in Burst settings).How it works
We use open-source Chrome addon - https://github.com/Andiedie/sync-my-cookie .
It allows setting what websites you want to sync, and puts a file with cookies into your Github profile as a Gist file.
Optionally, if you set an encryption password, it will encrypt contents, so it would be safe to share the gist.
The minimal required setup is:
That is it. Burst will read cookies on each search, apply to http client session.
Things to take into mind
Create sessions in the same network as Burst is running. It is a common practice to use IP-dedicated sessions, so IP address of Burst should be the same as the one used by Chrome to log in/authenticate.
It can be that there are multiple domains involved into authentication process on specific provider website. Chrome addon is syncing only the website you ask to, it does not store every cookie everywhere.
Providers configuration
To configure provider as the one that can re-use cookies to bypass authentication, you need to specify cookie name, that we try to find:
login_cookie
in this example is saying which cookie do we need (non expired one) to consider we have required cookie to skip authentication. Cookie is checked for the domain, provided inbase_url
parameter.The text was updated successfully, but these errors were encountered: