Re:Ask HN: Is anyone successfully self-hosting Firefox Sync?
by hosteur on Monday February 06, 2023 @06:40AM
(#34676063)
White-listing what addresses a web browser can reach seems to go against the intended use - you know, to browse the web.
[ Parent
| on HN ]
Re:Ask HN: Is anyone successfully self-hosting Firefox Sync?
by bluGill on Monday February 06, 2023 @09:07AM
(#34677427)
If you have something you are that concerned about then you should whitelist everything. Note that the whitelist needs to be one both sides, the server and the users. This along with lots of other security protections, some of which are a lot stronger than a whitelist.
Re:Ask HN: Is anyone successfully self-hosting Firefox Sync?
by parminya on Monday February 06, 2023 @04:08PM
(#34684352)
Instead of directly exposing the server to the internet, you could keep it behind a VPN. That way you only need to keep the VPN secure, the VPN serves as a whitelist.
Re:Ask HN: Is anyone successfully self-hosting Firefox Sync?
by alias_neo on Tuesday February 07, 2023 @03:17AM
(#34690127)
> White-listing what addresses a web browser can reach seems to go against the intended use - you know, to browse the web.
Agreed, but that was an extreme example. Blocking FFs known addresses should be sufficient with some additional network monitoring just in case.
I can't response to the rest of your comment, as my point was specifically about not needing to trust FF/MZ if you're running your own sync server. Once the software is within your network, it is entirely up to you, your tools and your skills to determine what does and does not leave it and to where.