Yes that's right, though others have pointed out applications that are
exceptions to this rule. But it's prudent to assume that the hosts.deny and
hosts.allow files aren't being consulted by applications not under inetd's
control.
Tony
On Wed, 13 Sep 2000, Zaleski, Matthew (M.E.) pushed some ti
4 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] What services are blocked by hosts.deny?
>
>
>
> Any services that don't use the inetd super server (from
> /etc/inetd.conf)
> are not covered by hosts.allow or hosts.deny.
>
> Tony
>
> On Tue, 12
Any services that don't use the inetd super server (from /etc/inetd.conf)
are not covered by hosts.allow or hosts.deny.
Tony
On Tue, 12 Sep 2000, Zaleski, Matthew (M.E.) pushed some tiny letters in this
order: >
> My primary way of securing my home Linux box (which is on a wireless
> broadband
> Hosts.deny works with inetd and tcpwrappers. Any service that is handled by
> inetd and passed to tcpwrappers can be configured by restrictions in
> hosts.deny.
>
> I am not aware that any other processes use hosts.allow/hosts.deny, but if
> anyone else knows, please mention it.
>
> You may al
Hosts.deny works with inetd and tcpwrappers. Any service that is handled by
inetd and passed to tcpwrappers can be configured by restrictions in
hosts.deny.
I am not aware that any other processes use hosts.allow/hosts.deny, but if
anyone else knows, please mention it.
You may also wish to look
