> but it's equally true that you could lock down a TCP socket to a specific process with about the same amount of work. How, actually? With UNIX sockets it can

> but it's equally true that you could lock down a TCP socket to a specific process with about the same amount of work. How, actually? With UNIX sockets it can be a matter of setting file ownership and mode (at worst, a chmod and a chown). What's the equally simple way to restrict access to a locally listening tcp socket?