Re: hurd does NOT need /hurd
Niels Möller <nisse@lysator.liu.se> wrote:
[...]
> For instance, I'm a little annoyed that the X-server I'm running is
> listening for connections on all interfaces. Perhaps I can work-around
> that by figuring out how linux fw-ing works this month, but I'd much
> prefer if my X-server listened *only* on it's AF_LOCAL socket, (and
> perhaps also on the localhost AF_INET interface (with forwarding
> disabled), if that's absolutely necessary to get X libraries and
> clients to work).
[...]
This has been changed in woody /for ages/ (afaict at least since
4.0.1-6, probably since the first official 4.0.1 release.)
README.Debian-upgrade.gz:
| TCP AND UDP PORT LISTENING DISABLED BY DEFAULT:
|
| To help ensure a more secure default configuration of your Debian
| system, several packages ship with network port listening disabled
| by default. This includes xdm, which does not listen on a UDP port
| for XDMCP requests; xfs, which does not listen on a TCP port for
| font requests; and the X server itself, which, when started by
| xdm, xinit, or startx, does not listen on a TCP port for client
| connections.
cu andreas
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: