Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Nummer anzurufen, sie per SMS zu kontaktieren oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Temporary bypass of cookie-removal-at-exit

  • Keine Antworten
  • 0 haben dieses Problem
  • 1 Aufruf
more options

Hi,

I have always used a "clear mostly everything" at exit approach to privacy. Before using FF I'd set exceptions for cookies that I prefer to keep (like search engine preferences) but I understand that isn't possible in FF, so I ended up using a different approach. On Unix-based systems I'd "quit" FF by with `pkill -9 -f firefox` (or waterfox). Somehow that worked (e.g. when restarting after an update) despite the obvious loophole it created but it was a welcome way to restart the browser without having to log in. Recently it stopped working though, and I find myself logged off every site I was logged in to, including Google and e.g. Whatsapp's web interface. Extremely annoying now that so many sites use 2FA.

Can you confirm this impression that the loophole has been closed, and security+privacy-related data is now removed at startup (too)?

Is there an way to quit/restart the browser without clearing this data, e.g. after an update or to release build-up RAM usage back to the system, while keeping the default "clear everything"? Is there an option not to lose logins etc. after a crash?

FWIW, the other reason I used this approach is because the open windows+tabs restore tended to be more reliable after a crash than after a normal shutdown (which would often miss a few tabs that I would not always miss at once).

Thanks in advance!

Hi, I have always used a "clear mostly everything" at exit approach to privacy. Before using FF I'd set exceptions for cookies that I prefer to keep (like search engine preferences) but I understand that isn't possible in FF, so I ended up using a different approach. On Unix-based systems I'd "quit" FF by with `pkill -9 -f firefox` (or waterfox). Somehow that worked (e.g. when restarting after an update) despite the obvious loophole it created but it was a welcome way to restart the browser without having to log in. Recently it stopped working though, and I find myself logged off every site I was logged in to, including Google and e.g. Whatsapp's web interface. Extremely annoying now that so many sites use 2FA. Can you confirm this impression that the loophole has been closed, and security+privacy-related data is now removed at startup (too)? Is there an way to quit/restart the browser without clearing this data, e.g. after an update or to release build-up RAM usage back to the system, while keeping the default "clear everything"? Is there an option not to lose logins etc. after a crash? FWIW, the other reason I used this approach is because the open windows+tabs restore tended to be more reliable after a crash than after a normal shutdown (which would often miss a few tabs that I would not always miss at once). Thanks in advance!

Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.