Live data from Hacker News

Self-Hosting a Firefox Sync Server

blog.diego.dev

21–30 of 91 posts

Re: Self-Hosting a Firefox Sync Server

#21
post #7

Great timing, with Mozilla's new privacy policy problems the other day

why would those matter since your sync data is encrypted and they can't see it anyway?

Why have your data sitting on a timebomb when quantum risks are just around the corner. Self host if you care about your data!

Re: Self-Hosting a Firefox Sync Server

#22

I did that for a while, including hosting the auth myself. Then I realized Mozilla is probably one of the few companies I trust with my data, even though it's probably misplaced trust. The sync server is relatively straightforward to setup, but auth is quite more involved. I don't think it's worth it, compared to using the public hosted service

Mozilla just burned out the last remaining bits of good will with the "terms of use" fiasco. At least there's LibreWolf to keep a privacy-respecting fork.

Re: Self-Hosting a Firefox Sync Server

#23
post #10

What's the privacy benefit, given that Firefox Sync is E2E encrypted? https://support.mozilla.org/en-US/kb/sync

To best of my awareness, the login page (including JS code) is still served over the Internet, and encryption keys are derived solely from the password. That’s not a good design for something as sensitive as one’s full browser data.

send a pr.

but don't know how adding a key owned by moz would make this more trustworthy

Re: Self-Hosting a Firefox Sync Server

#24
post #7

Great timing, with Mozilla's new privacy policy problems the other day

why would those matter since your sync data is encrypted and they can't see it anyway?

because they can update the client tomorrow to not use e2e...

meta did it. google did it. so not without precedent.

Re: Self-Hosting a Firefox Sync Server

#25
post #7

Great timing, with Mozilla's new privacy policy problems the other day

why would those matter since your sync data is encrypted and they can't see it anyway?

If you self host, you don't need to wonder whether you need to respect their acceptable use policy.

Re: Self-Hosting a Firefox Sync Server

#26
post #9
post #5

Would be nice if librewolf and WaterFox changed their flow to make it clear that Mozilla's Sync Server is being used, and make it opt in with something like: To sync please select one of the options below: [x] Custom Sync Server: ___________ [ ] Mozilla Sync

LibreWolf is opt in and if you click the checkbox named "Firefox Sync" thinking you're getting some kind of sync that isn't Firefox Sync I don't think there's any UI change that can help you.

Your parent comment's idea is quite sensible, no need to be contemptuous like this. Firefox branding is a mess, being both a browser and a set of services. It's reasonable to mix things up or to be confused.

Re: Self-Hosting a Firefox Sync Server

#27

I did that for a while, including hosting the auth myself. Then I realized Mozilla is probably one of the few companies I trust with my data, even though it's probably misplaced trust. The sync server is relatively straightforward to setup, but auth is quite more involved. I don't think it's worth it, compared to using the public hosted service

Mozilla rebranding themselves as an advertising company and getting the majority of their funds (and assumedly direction) from Google should have you at least questioning that trust.

Re: Self-Hosting a Firefox Sync Server

#29

Earlier quoted context omitted.

Maybe eventually the whole stack can make its way into a docker container with a shell script for config.

Maybe it's just me but having dedicated employee's to manage security is a prerequisite for me; atleast I could point my finger at someone if things happen.

I personally don't see the value in that. I'd rather spend time fixing something than getting people to fix it for me, and having someone just to point fingers at them after a failure feels cowardly. But maybe I'm just not a managerial type.

Re: Self-Hosting a Firefox Sync Server

#30

Earlier quoted context omitted.

Maybe eventually the whole stack can make its way into a docker container with a shell script for config.

Maybe it's just me but having dedicated employee's to manage security is a prerequisite for me; atleast I could point my finger at someone if things happen.

I completely understand the feeling, but when's the last time pointing fingers actually got you anywhere? :)
Post reply on HN