[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] new openssl vulnerabilities
- Subject: Re: [cobalt-users] new openssl vulnerabilities
- From: Parker Morse <morse@xxxxxxxxxxx>
- Date: Tue Jul 30 09:20:56 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
On Tuesday, July 30, 2002, at 11:57 AM, Network Operations wrote:
how would you used hosts.deny to block all access to port 22 except
from a list of specified ip's?
Or would hosts.deny even be what you want to use?
You could use hosts.deny with its (evil?) twin, hosts.allow. See "man
hosts.allow" (or "man hosts.deny") for more details, but here's the key
part of the man page:
---begin excerpt---
The access control software consults two files. The search stops at the
first match:
o Access will be granted when a (daemon,client) pair matches an entry in
the /etc/hosts.allow file.
o Otherwise, access will be denied when a (daemon,client) pair matches
an entry in the /etc/hosts.deny file.
o Otherwise, access will be granted.
A non-existing access control file is treated as if it were an empty
file. Thus, access control can be turned off by providing no access
control files.
---end excerpt--
So I would try adding your specified IPs to hosts.allow, and then put the
appropriate "deny all" rule in hosts.deny.
pjm