I've been trying to configure my laptop to suit my needs, which differs from those on desktop. Basically, I trust both devices due to full-disk encryption, but it's possi… (funda kabanzi)
I've been trying to configure my laptop to suit my needs, which differs from those on desktop. Basically, I trust both devices due to full-disk encryption, but it's possible to steal my laptop while powered on and unlocked. Hence my laptop approach is strict while adding a few exceptions that rely on successful authentication without remembering passwords.
I find it quite hard to manage exceptions. I've spend a couple of hours reading through this forum as well as numerous FAQs and guides, yet it appears there are a lot of conflicting options that override certain settings. The entire process is pretty counterintuitive and could use an overhaul from a UX perspective, where a simplification of the process might also result in the resources becoming more useful.
Anyway, one of my issues is that it appears I can't use asterisk * when defining URL exceptions for cookie settings. Second, unless explicitly defined, the protocol defaults to http and not https. I guess I should ask what happens before complaining too much. Example time:
1: I add the URL 'example.com'
2: Firefox converts it to 'http://example.com'
3: I add the URL 'https://example.com'
How will each of these exceptions work for the following:
And how can I mitigate this without a regex or similar, short of manually adding an extensive list of possible variations in between https:// and .example.com? To clarify, I'll need an exception for something like https://*.example.com
Finally, how is this affected by individual settings in the sections Enhanced Tracking Protection, Cookies and Site Data, and History? Any pitfalls I should be aware of?