News for hackers. Stuff that matters.
Re:Private by Design: How We Built Firefox Sync by NewEntryHN on Wednesday November 14, 2018 @05:48AM (#18448938)
Trusting the binary is a one-time effort. Here you have to trust the JS everytime you authenticate.
Re:Private by Design: How We Built Firefox Sync by Faark on Wednesday November 14, 2018 @07:46AM (#18449411)
Even one-time, comparing the hash of a git commit or an installer is annoying but practically doable. I'd have no idea how to safely do something like this for a website. And I for sure ain't able to audit those ~200kb js by myself.
Re:Private by Design: How We Built Firefox Sync by joekrill on Thursday November 15, 2018 @06:08AM (#18458384)
But my point is you also have to trust that your underlying OS, or chipset, or even some other software on your computer doesn't have some way to thwart the entire effort. If the thing you're using the do your verification is itself compromised, then you're just as screwed.
Re:Private by Design: How We Built Firefox Sync by IshKebab on Wednesday November 14, 2018 @10:35AM (#18450598)
So you never update Firefox? For most users it automatically updates itself.
Re:Private by Design: How We Built Firefox Sync by fro0116 on Wednesday November 14, 2018 @06:11AM (#18449041)
For this use case, authenticating is a one-time effort as well, per browser. If you're authenticating again, you're almost certainly doing it on a different device/browser, at which point you'd have to verify the new browser binary anyways.
Re:Private by Design: How We Built Firefox Sync by eadmund on Wednesday November 14, 2018 @07:22AM (#18449310)
Sign-ins to Firefox Accounts (used to access Mozilla services as web pages) don’t expire after some time? I didn’t know that.