Robert, I've never used the 'except' directive, so I can't address why that
does / doesn't work. Here's a snippet from 'man hosts.allow' that might
clear things up somewhat:
ACCESS CONTROL FILES
The access control software consults two files. The search
stops at the first match:
^^^^^^^^^^^^^^^^^^^^^^
ˇ Access will be granted when a (daemon,client) pair
matches an entry in the /etc/hosts.allow file.
ˇ Otherwise, access will be denied when a (dae
mon,client) pair matches an entry in the
/etc/hosts.deny file.
ˇ 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.
I believe if you loose the 'except' directive in hosts.deny, then it will
work as you expect.
HTH,
Mike
-----Original Message-----
From: Robert Canary [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 07, 1999 2:01 AM
To: [EMAIL PROTECTED]
Subject: host allow/deny
Okay this just isn't working very well.
In my host.allow I have
ALL:.mydomain.net
ALL:.workplace.com
In my host.deny I have
ALL:ALL except .mydomain.net
How ever I can't get anything to connect from workplace.com unless I
include workplace.com in the exception list in the host.deny like this.
ALL:ALL except .mydomain.net .workplace.com
And I can't get NFS to allow a mount a mount from a local machine in the
mydomain.net unless I include it as an exception, also. Does the
host.allow do *anything*? Why does this not work?
Thanks in Advance :-)
--
robert canary
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
