| Summary: | The port 20048 needs to be open for automount access through /net. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Xuo <xuoy> |
| Component: | Release (media or process) | Assignee: | Guillaume Rousse <guillomovitch> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | CC: | sysadmin-bugs, xuoy |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | nfs-utils-2.3.4-3.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Xuo
2020-01-11 17:28:06 CET
Assigning initially to Guillaume as the nfs-utils maintainer. Assignee:
bugsquad =>
guillomovitch Technically, it is quite difficult to interact with a firewall without knowledge of local filtering policy. Which source address should be allowed, for instance ? And if you're paranoid enough to install a local firewall, usually, it is to control your network traffic finely, so I don't see the point of automatically opening anything on install. But more generally, NFS is a network service, as well as many others we ship in the distribution. Do we really need to explain anyone installing such a service than he also need to configure its firewall properly ? We may as well explain he needs to configure the service, read related documentation, or any other implicit expectation. And for every similar service in the distribution, such as samba, apache, etc... Hi, I didn't think I was paranoid if I wanted to enable a local firewall. Maybe I am. In the MCC, when I want to enable NFS, the nfs ports are automatically open without the need of reading any doc. This was my request. Regards. Xuo. CC:
(none) =>
xuoy |