Tim: > > Correct that localhost (127.0.0.1) should only be talking amongst > > itself, but I was a bit concerned that the "home" zone might stop > > something it oughtn't to within that.
Marco Moock: > What should it stop? > External traffic targeted at 127.0.0.0/8 or ::1 and addresses to the MAC > address of the system? > As a general rule, 127.x.y.z should *only* be communicating with 127.x.y.z (and it's IPv6 equivalents). But do we allow all ports within itself? Normally yes, as we're not installing untrustworthy things on our PCs (not that I call a web browser trustworthy). Should we restrict some? We, as the average user, don't know all the internal communication a system is doing. And I recall on other computer systems that good advice was to make sure firewall rules for loopback interfaces were fully open to prevent unexpected nuisances. When I look at the "home" zone on other interfaces, I can see that it's not a free-for-all. There are some preselected allowed services, and most other things are unticked. There's another issue that often popped up with Fedora in the past, not sure about now. People would often add the local hostname to the 127.0.0.1 line in the /etc/hosts file, confusing some aspects of networking. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 (yes, this is the output from uname for this PC when I posted) Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
