> | Connections from remote clients are treated as untrusted unless
> | they originate from a privileged port, and requests are only
> | serviced if they fall on filesystems which have been exported to the
> | requesting host.
>
> If I'm interpreting this correctly, anybody on the net that has root
> on their computer will be treated as trusted by fam on my computer.
Sort of; it's anybody who has root on a computer that you've NFS-exported the
filesystem to. fam will believe them when they say "UID so-and-so wants to
monitor this file," but if the file they're asking for doesn't fall on a
filesystem that they could have mounted, fam tells them the file doesn't
exist.
> Also, it would be nice to get away from RPC services, since they are
> so difficult to block from the outside world. At the very least,
> services (such as fam) that are intended for local use should only
> listen on the loopback interface.
Yeah... there's an only-slightly-documented way to get fam to run local-only
(see the INSTALL file--you have to take it out of inetd.conf and put it in
an init script--and it still registers with the portmapper), but I don't
think fam is intended to be only for local use. "In theory," it shouldn't
matter where your filesystem is mounted from; you ask fam to monitor it, and
fam tries to pass your request on to fam on the host serving the files so
that you still get notification when your files changed without having to
poll over NFS.
--Rusty
--
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx
|