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

How to protect URL? #54

Open
HoffiConfusion opened this issue Jan 22, 2019 · 4 comments
Open

How to protect URL? #54

HoffiConfusion opened this issue Jan 22, 2019 · 4 comments
Labels

Comments

@HoffiConfusion
Copy link

Hello,

how can I protect all future Cookies from xyz.com?
It means cookie-quick-manager should not work for xyz.com.

Thank you!

@HoffiConfusion
Copy link
Author

Nobody knows?

@ysard
Copy link
Owner

ysard commented Jun 21, 2019

Hi, please excuse me for the response time;

A simple implementation can be done; it would automatically protect all future cookies from all domains with a cookie already protected (if I understand correctly).

But I think the use case is borderline and is useful only briefly (for testing). Indeed it would be counterproductive to protect cookies without control; some sites can indeed create dozens of cookies quickly and it is precisely the sites for which the protection of some cookies allows to easily remove all others in a few clicks.

Moreover, it would be quite complex today to implement this functionality for some particular domains and not the others.

The role of the protection function is originally dedicated solely to the GUI (ability to massively delete cookies while retaining some).

As I said in another issue (#55), it is not possible to prevent a site from erasing a cookie, or modifying it (at least in this addon that is not an firewall/ad-blocker like uMatrix.). I can recreate an erased cookie, or even restore a cookie in a previous version (more complex and not implemented) but there will always be a short period of time where the website has had full powers over its cookies. The first edge effect is that it can go unnoticed by a user...

@ysard ysard added the question label Jun 21, 2019
@HoffiConfusion
Copy link
Author

Hm, okay, mayby I mean something else. Not preventing a site from erasing a cookie, rather protect cookies from deleting by cookie-quick-manager

grafik

cookie-quick-manager delete all unprotektet cookies 2 seconds aftr restarting the browser. Thats the great work.

in the programm I can protekt very specific a single cookie, not to delete.

And I thougt there would be an easy way to protect all cookies from a specific domain: 2 seconds after restarting the browser delete all cookies without the cookie from xyz.com.

specifically, it is about cookies from a transport company. It is comfortable when the last connections are saved. But I do not know, how to do this.

@ysard
Copy link
Owner

ysard commented Jun 21, 2019

And you can not guarantee once and for all that cookies can all be protected?
I mean, the cookie names are not predictable, which prevents you from building a list?

I advise you to use uMatrix for this.
Your use case is described here: https://github.com/gorhill/uMatrix/wiki/Cookies

1 - Go in the parameters of the addon, then tab "my rules".
Then just add one or two rules for cookies:

  • Block all cookies from anything to anything;
  • Then allow all cookies from your website.
* * cookie block
your_website * cookie allow

2 - Go in the parameters of the addon, then tab "parameters".
Check the "delete blocked cookies" checkbox.

3 - Go to aliexpress for example

  • uMatrix shows a number of cookies which are blocked
    tmp2

  • check the cookies in CQM
    image

  • quit aliexpress and check in CQM
    => No cookie to display

4 - Go to your_website

  • uMatrix shows a number of cookies allowed (the cookie column should be green)
  • check them in CQM
  • quit your_website
  • check the cookies in CQM
    => Cookies are still here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants