Title: RE: hosts.allow
Can httpd or snmpd accesses be restricted using a hosts.deny and hosts.allow combination?
-Original Message-
From: Jerry Winegarden [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 04, 2002 7:26 PM
To: [EMAIL PROTECTED]
Subject: Re: hosts.allow
On Thu, 4 Jul
In the following hosts.allow, is the LOCAL necessary?
ALL: LOCAL
ALL: 192.168.1.
jay
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
On Thu, Jul 04, 2002 at 05:00:15PM -0400, Jay Daniels wrote:
>
> In the following hosts.allow, is the LOCAL necessary?
>
> ALL: LOCAL
> ALL: 192.168.1.
Hmmm...depends what you want this to do. It is different than the
second line. LOCAL matches any hostname without a '.&#x
erm
it allows certain address acces to your machine on certain ports/services
ie u can only allow a certain ip to telnet
and hosts.allow takes precedence over hosts.deny
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Chad and Doria Skinner
Sent
> Do you mean tcpwrappers ?
Bingo! Thank You
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29-Apr-2002/18:18 -0500, Chad and Doria Skinner <[EMAIL PROTECTED]> wrote:
>I'm feeling fried at the moment...hosts.allow and hosts.deny are referred
>to by a name, but I can not remember what it is does anyone know? I know
>t
*** REPLY SEPARATOR ***
On 29/04/2002 at 6:18 PM Chad and Doria Skinner [EMAIL PROTECTED]
[gregausit/redhat-list] wrote:
>I'm feeling fried at the moment...hosts.allow and hosts.deny are referred
>to
>by a name, but I can not remember what it is does anyone kn
I'm feeling fried at the moment...hosts.allow and hosts.deny are referred to
by a name, but I can not remember what it is does anyone know? I know the
name is used when compiling some software to force it to use the files, but
I'm at a loss. Ideas?
Th
> From: Jerry Winegarden <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: Re: /etc/hosts.allow ssh : all
> Reply-To: [EMAIL PROTECTED]
>
> There is one possibility these days: use a dynamic DNS registration
> service (e.g. dyndns.org) to register y
On Mon, 30 Apr 2001, Stuart Clark wrote:
> /etc/hosts.allow
> ssh: all
>
> Is this a good idea or should i consider something like this ?
>
> /etc/hosts.allow
> ssh: xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx
>
First of all, I'm assuming that you have hosts.deny with: AL
I can't find it back right now, but if my memory serves me well I think
have read somewhere that sshd (at least from OpenSSH) uses the
hosts.deny and hosts.allow files on it's own, without being run by
inetd.
Regards
Gustav
"John D. Hardin" wrote:
>
> On Sun, 29 A
On Sun, 29 Apr 2001, Mike Burger wrote:
> Most ssh daemons run as a standalone daemon, and don't interact
> with inetd/xinetd and don't pay any attention to hosts.allow or
> hosts.deny.
Be careful there. tcpwrappers is a compile-time option in sshd. And
it's possib
, and don't interact with
>inetd/xinetd and don't pay any attention to hosts.allow or hosts.deny.
sshd is built with tcp wrappers support wether or not you run it
from inetd. The line granting access in hosts.allow/hosts.deny
should read:
sshd:
Again, this works with sshd r
On Mon, 30 Apr 2001 at 12:44am (+1000), Stuart Clark wrote:
> /etc/hosts.allow
> ssh: all
>
> Is this a good idea or should i consider something like this ?
>
> /etc/hosts.allow
> ssh: xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx
>
It depends on what you're trying to acheive
Actually, unless you're running ssh out of xinetd/inetd, that won't do any
good at all.
Most ssh daemons run as a standalone daemon, and don't interact with
inetd/xinetd and don't pay any attention to hosts.allow or hosts.deny.
On Mon, 30 Apr 2001, Stuart Clark wrote:
>
/etc/hosts.allow
ssh: all
Is this a good idea or should i consider something like this ?
/etc/hosts.allow
ssh: xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
>From: Dave Wreski <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: hosts.allow & hosts.deny
>Date: Sun, 8 Oct 2000 17:47:06 -0400 (EDT)
>
>
> > ALL: ALL: (/usr/sbin/wall test) &
> >
> > Of course, this do
> ALL: ALL: (/usr/sbin/wall test) &
>
> Of course, this does not do anything but broadcast "test" to all of the
> consoles, but it should have executed the command when i tried to telnet
> into my machine, which it did not. Furthermore, it did not even allow me
> into the machine using telne
I am trying to set up some semblence of security on my machine with linux.
(redhat 6.2) Unfortunately, I have run into a small problem and was hoping
someone might be able to help me with it. I would like to set up
hosts.allow and hosts.deny to send me an email whenever someone
telnets
of
.domain.com" and allow me access. Is that what you wanted? I highly doubt
it.
I think you probably want to be using IP addresses in your hosts file, and
not domains.
On Wed, 18 Mar 1998, Gibson, Todd wrote:
> (snip)
> > And list individually the services you want t
(snip)
> And list individually the services you want to allow in
/etc/hosts.allow:
> ALL: 127.
> in.ftpd: .my.domain
> in.telnetd: .my.domain
> in.popd: .my.domain
(snip)
What is the proper order for /etc/hosts?
> Try
> /etc/hosts.allow:
> ALL: 127.
>
> /etc/hosts.deny
> ALL:ALL
Ah, this worked great! Reading the man page, I'm not sure why the symbolic
names didn't work, but the 127. numeric is quite acceptable.
Thanks for this and all suggestions!
-Michael
--
&quo
rom doing an rlogin or fetchmail from my machine back to my machine.
In hosts.allow add:
ALL: XXX.XXX.XXX.XXX
in.telnetd: XXX.XXX.XXX.XXX
imapd: XXX.XXX.XXX.XXX
In hosts.deny:
ALL: ALL
However try using ssh instead of rlogin if you want to be secure.
--
Curtis Consulting
Try
/etc/hosts.allow:
ALL: 127.
/etc/hosts.deny
ALL:ALL
Michael George wrote:
> Hello all!
>
> Even though I just have dial-up access to the net, I put "ALL: ALL" in my
> /etc/hosts.deny file to keep intruding processes out. However, this also
> keeps me from doi
Leave /etc/hosts.deny with all:all
then have in /etc/hosts.allow all:192.168.0.
192.168.0. obviously being your subnet if that won't work (it should)
have in /etc/hosts.allow
all:192.168.0.1
all:192.168.0.2
etc
Dan
At 02:13 PM 3/16/98 +, Michael George wrote:
>Hello all!
ooking for a way to loopback to
this host and allow access. I have tried "ALL: ALL" in hosts.deny and then
"ALL: LOCAL" in hosts.allow, but that doesn't help. Neither does "ALL:
localhost ." in the hosts.allow file. The
only thing that seems to work for lettin
26 matches
Mail list logo
