A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.96K Posts
- 74.6K Comments
- Modlog
According to LocalSend docs these are the ports that need to be opened: Multicast (UDP) Port: 53317 Address: 224.0.0.167 HTTP (TCP) Port: 53317 AFAIK macOS firewall is app-based, at least in the GUI. So depending on how you installed LocalSend, you may have to add it to the list of allowed apps: https://support.apple.com/en-ca/guide/mac-help/mh34041/mac
You may be able to add the ports above to /etc/pf.conf manually, but AFAIK messing with pf on macOS is not recommended.
The other thing I wanted to ask is about Vallum. If you have it running on that Mac, would it not “take over” the macOS firewall?
i will try these when i go back.
what do you mean by “take over”?
i prefer vallum as it permits more precise rules. macOs firewall is just an on/off switch and by default gives permission to all apple processes