Live data from Hacker News

Facebook Container for Firefox

mozilla.org

361–370 of 446 posts

Re: Facebook Container for Firefox

#362

Earlier quoted context omitted.

I agree, your description is more why I like it -- the only websites that get to save any state are the ones I pick to open in specific named containers and which I also specifically granted permissions to with uMatrix (RIP). Everything else opens links in a new container with the hope to make it as close as possible to looking like a different person clicked that link. I know it won't work that well since the IP doe…

I share the same goals; thanks for the succinct description. Discussion upthread made me interested to see whether I can route temporary containers through tor, to make this protection stronger — see https://news.ycombinator.com/item?id=24853320 It's not super high on my list of priorities though, probably won't get to it for a month or two.

Oh, that'd be very neat if it made separate container tabs look like different tor sessions. Very clever! I suppose there's little short of that which would stand a real chance of working...

Re: Facebook Container for Firefox

#363

Earlier quoted context omitted.

I log into roughly 20 AWS accounts/day. Container tabs make that work. I can compare things side by side or just work on two tasks at once.

Holy moly, why 20 accounts?

Standard practice in larger scale.

I run big fleets, 100s of hosts 1000s of containers in most AWS regions. Most of the control plane is automated, but when that breaks, or there are issues in the data plane, I might log into read logs, look at metrics, force scaling actions, or just general investigation tasks.

I also use different accounts for permissions boundaries. Data shared between multiple teams might go in one account. The apps can access the data but maybe the interns can only access the app account while the SR. Eng(s) + current oncall have full read only access to the data for investigation. A second RW-Data oncall might have access to the DB account in each region. Ever data storage account also has a limited access cross account Data replication/backup account.

+ I help people out. 'Can you look at this? . . .'

In the end, there are account specific errors that can be caused in your infra, IAM rolls, keys, throttling, malicious access that are easily prevented with least access in per account buckets. So I end up with multiple accounts in each region.

Re: Facebook Container for Firefox

#365
post #357

Earlier quoted context omitted.

Holy moly, why 20 accounts?

AWS credits? You can get a bunch of free credits for each account, and then build an abstraction around boto3 to make 20 accounts look like 1 account to you.

meh, compute cost almost always costs less than dev time. I use multiple accounts for separation of duties, cost, access, and blast radius. Most services I run blow through the free tier in minutes.

I do have scripts that spin up accounts as needed and I just have a bucket for 'free Tier account access ending' emails.

Re: Facebook Container for Firefox

#366

Earlier quoted context omitted.

Holy moly, why 20 accounts?

It's not that unusual to use separate AWS accounts as blast-barriers. I.e. they contain the damage that might occur due to a leak etc. I typically use 2 (prod & non-prod) for each major product/offering, plus a centralised one to manage policies, billing etc for all the sub accounts. They add up pretty quickly.

I use an account for $service-$stage-$region- then I run most services in every available region

so:

main-service_prod_us-east-1_dataStore

main-service_prod_us-east-1

main-service_test_us-east-1_dataStore

main-service_test_us-east-1

main-service_beta_us-east-1_dataStore

main-service_beta_us-east-1

* regions

Adds up pretty quickly.

Re: Facebook Container for Firefox

#367

Earlier quoted context omitted.

As long as you're spoofing your fingerprint info (you can randomly change things like fonts, video cards, battery life, plugins etc) it doesn't matter how unique you are because every time you visit the site you'll be unique just like everyone else who is either a first time visitor or does the same. That seems way more effective than trying to hide in a "crowd" when even the smallest consistent deviation in an ever…

Couldn't the frequency of profile information itself be considered a uniquely identifying attribute? Couple that with something that's harder to change on every request (such as IP address) and I imagine you can confidently build a profile out of that.

frequency of changes could be an issue in cases where connections are continuous, but for most browsing it shouldn't be a huge problem. Your information will have changed multiple times between requests. The IP problem is larger, but can be mitigated by the use of VPN, TOR, or shared connections (school, workplace, public wifi etc). I think the real takeaway is that there is no perfect solution, only means which make the work of people attempting traffic correlation more difficult. For services you're already logged into (facebook, steam, reddit, insta, youtube, HN) the battle is already lost. Blocking trackers and ads helps prevent 3rd parties from building a profile of your actions across the web, but all we can ever hope to do is make the record less complete. We're all vulnerable. Now that ISPs are able to decrypt much of our traffic and sell our entire browsing histories alongside our names it's not something I see being solved anytime soon.

Re: Facebook Container for Firefox

#370
post #51

If you enable the First-Party Isolation preference in about:config then this is more effective site isolation and is automatic for all sites.

Do you use this for every day browsing? Does it break anything?

Yes.No, it does not break anything for me, and I browse a ton of websites.
Post reply on HN