Has anything relating to those files changed between jessie and stretch
to affect cups being blocked?
Would a line in the allow file ALL: localhost:631 help or is the syntax
incorrect?
s it works with tcpwrappers yet
it seems to ignore /etc/hosts.deny ?
Thanks,
Jon
root@mail:/usr/share/doc# ldd /usr/sbin/sendmail |grep 'libwrap'
libwrap.so.0 => /lib/i386-linux-gnu/libwrap.so.0 (0xb7525000)
root@mail:/usr/share/doc# cat /etc/debian_version
8.2
I want to use sendmail with tcp wrappers but it does not seem to play,
it looks like it was compiled with
On Tue, 10 Jul 2012 20:18:07 +0200, Zdenek Herman wrote:
> On 10/07/12 17:29, Camaleón wrote:
(...)
>>> Ah, how curious... It seems to be documented here:
>>>
>>> 4.2.2. Connecting to the MySQL Server
>>> http://dev.mysql.com/doc/refman/5.6/en/connecting.html
(...)
>>>
>> Camaleón is correct.
On 10/07/12 17:29, Camaleón wrote:
On Tue, 10 Jul 2012 18:09:42 +0200, Zdenek Herman wrote:
On Mon, 09 Jul 2012 20:11:10 +0200, Zdenek Herman wrote: (please, reply
at the bottom)
Dne 9.7.2012 16:52, Camaleón napsal(a):
(...)
I don't know why does not work for you. Take a look into this art
On 10/07/12 17:29, Camaleón wrote:
On Tue, 10 Jul 2012 18:09:42 +0200, Zdenek Herman wrote:
On Mon, 09 Jul 2012 20:11:10 +0200, Zdenek Herman wrote: (please, reply
at the bottom)
Dne 9.7.2012 16:52, Camaleón napsal(a):
(...)
I don't know why does not work for you. Take a look into this art
On Tue, 10 Jul 2012 18:09:42 +0200, Zdenek Herman wrote:
> On Mon, 09 Jul 2012 20:11:10 +0200, Zdenek Herman wrote: (please, reply
> at the bottom)
>>> Dne 9.7.2012 16:52, Camaleón napsal(a):
(...)
>> I don't know why does not work for you. Take a look into this article
>> that shows a few sampl
On Mon, 09 Jul 2012 20:11:10 +0200, Zdenek Herman wrote: (please, reply
at the bottom)
Dne 9.7.2012 16:52, Camaleón napsal(a):
On Sun, 08 Jul 2012 22:26:11 +0200, Zdenek Herman wrote:
(...)
When I set hosts.deny ALL: ALL and hosts.allow is empty. I can allow
connect to MySQL from anywhere
On Mon, 09 Jul 2012 20:11:10 +0200, Zdenek Herman wrote:
(please, reply at the bottom)
> Dne 9.7.2012 16:52, Camaleón napsal(a):
>> On Sun, 08 Jul 2012 22:26:11 +0200, Zdenek Herman wrote:
>>
>> (...)
>>
>>> When I set hosts.deny ALL: ALL and hosts.allow
ay be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.
mysql>
________
and in hosts.deny is ALL:ALL
Zdenek Herman
zdenek.her...@ille.cz
Dne 10
On Mon, Jul 9, 2012 at 11:41 PM, Zdenek Herman wrote:
> My hosts.deny
> # /etc/hosts.deny: list of hosts that are _not_ allowed to access the
> system.
> # See the manual pages hosts_access(5) and
> hosts_options(5).
> #
> # Example:ALL: some.ho
My hosts.deny
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the
system.
# See the manual pages hosts_access(5) and
hosts_options(5).
#
# Example:ALL: some.host.name, .some.domain
# ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If
On Sun, 08 Jul 2012 22:26:11 +0200, Zdenek Herman wrote:
(...)
> When I set hosts.deny ALL: ALL and hosts.allow is empty. I can allow
> connect to MySQL from anywhere - settings in hosts.allow and hosts.deny
> are ignored.
(...)
I wonder if you aren't just missing the daemon to
Hello
I have problem with MySQL and control access by TCP wrapper in Debian
Squeeze.
MySQL is compiled correctly with libwrap library:
ldd /usr/sbin/mysqld | grep libwrap
libwrap.so.0 => /lib/libwrap.so.0 (0x7f145d28d000)
When I set hosts.deny ALL: ALL and hosts.allow is empty.
I
Hello Clive
Thanks for pointing me to to ipcalc,
I noticed smb.conf has a commented entry for 127.0.0.0/8
This would cover the whole local subnet:
HostMin: 127.0.0.1
HostMax: 127.255.255.254
Does it make sense to cover more than 127.0.0.1 and 127.0.1.1 in
/etc/hosts.allow ?
I don't kn
l smb.conf entries + daemon mode.
The server is behind a router/firewall, it should be safe as it is.
On 26.04.2012 12:54, shawn wilson wrote:
Juan is correct. However my two cents - don't rely on hosts.allow and
hosts.deny for anything. Just use iptables rules to do this type of thing.
A
Hi Tuxoholic,
[...]
> With this smb.conf tweaking it works fine, but why could smbd/nmbd run past
> /etc/hosts.allow and /etc/hosts.deny without those lines in smb.conf?
Already answered by Juan Sierra Pons.
> To my limited CIDR understandig a /32 mask should restrict
Juan is correct. However my two cents - don't rely on hosts.allow and
hosts.deny for anything. Just use iptables rules to do this type of thing.
Also, most don't consider samba to be a very secure service (last CVE was
only a few weeks ago) so be very careful with this service.
On Apr
10 MYSERVER
>
> cat /etc/hosts.allow
> #ALL: localhost 127.0.1.1 192.168.2.0/24
> ALL: localhost 127.0.1.1 192.168.2.0/32
>
> /etc/hosts.deny
> ALL: ALL
>
> With this ruleset in place nmbd broadcasts still pull through and cifs mounts
> are still possible, whereas ssh/rsh
/24
ALL: localhost 127.0.1.1 192.168.2.0/32
/etc/hosts.deny
ALL: ALL
With this ruleset in place nmbd broadcasts still pull through and cifs mounts
are still possible, whereas ssh/rsh access is no longer possible.
To get rid of nmbd/smbd access I have to tweak smb.conf additionally:
/etc/samba
On 23/12/11 13:20, Scott Ferguson wrote:
> On 15/12/11 20:56, perlj...@gmail.com wrote:
>> After a manual entry in /etc/hosts.deny
>>
>> ip didn't blocked
>>
>> ALL: 151.12.xxx.xxx
>>
>> I wonder why?
>>
>> I use denyhosts for automati
On 15/12/11 20:56, perlj...@gmail.com wrote:
> After a manual entry in /etc/hosts.deny
>
> ip didn't blocked
>
> ALL: 151.12.xxx.xxx
>
> I wonder why?
>
> I use denyhosts for automatic entries
>
> Thank you in advance
>
> Nikos
>
>
On 12/15/2011 01:40 PM, Raf Czlonka wrote:
> On Thu, Dec 15, 2011 at 09:56:48AM GMT, perlj...@gmail.com wrote:
>> After a manual entry in /etc/hosts.deny
>>
>> ip didn't blocked
>>
>> ALL: 151.12.xxx.xxx
>>
>> I wonder why?
>
> What do y
On Thu, 15 Dec 2011 11:56:48 +0200
perlj...@gmail.com wrote:
> After a manual entry in /etc/hosts.deny
>
> ip didn't blocked
>
> ALL: 151.12.xxx.xxx
>
> I wonder why?
>
Do a test without the x's, endind with just a dot
ALL: 151.12.
> I use denyhosts
On Thu, Dec 15, 2011 at 09:56:48AM GMT, perlj...@gmail.com wrote:
> After a manual entry in /etc/hosts.deny
>
> ip didn't blocked
>
> ALL: 151.12.xxx.xxx
>
> I wonder why?
What do you mean by didn't get blocked?
Using what service/port?
Does your service
After a manual entry in /etc/hosts.deny
ip didn't blocked
ALL: 151.12.xxx.xxx
I wonder why?
I use denyhosts for automatic entries
Thank you in advance
Nikos
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
an hosts.allow'
> 1.
> hosts.allow
> #
> mysqld: 192.168.2.0/255.255.255.0
>
>
> hosts.deny
> #
> mysqld: ALL
--
Kind Regards,
Michael Shuler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mysqld in hosts.allow / hosts.deny ?
===
Now, Can i use tcpwrapper with mysql on debian ?
If it can be used.
Which config. that i correct ?
( If i want to only allow from my LAN ( 192.168.2.x netmask 255.255.255.0 )
1.
hosts.allow
#
mysqld: 192.168.2.0
Why not uncomment line 19 in /etc/hosts.deny? Then use /etc/hosts.allow
specifically to allow certain ips. The /etc/hosts.allow is checked first
and anything not found in it that's covered by /etc/hosts.deny is supposed
to be blocked. Even so, I'd be looking at the system with last
On Thursday 01 June 2006 11:59 pm, Chuck Payne wrote:
> Hi,
>
> I am being hit by some ips that I like to block. I like to know how can
> I use hosts.deny for the ALL statement
After all the comments, aka lines that look like this:
# This is a comment, after these put
ALL:
Chuck Payne <[EMAIL PROTECTED]>:
>
> I am being hit by some ips that I like to block. I like to know how can
> I use hosts.deny for the ALL statement
Have you looked at the contents of hosts.deny? I find this in there:
# Example:ALL: some.host.name, .some.domai
Chuck Payne wrote:
> Hi,
>
> I am being hit by some ips that I like to block. I like to know how can
> I use hosts.deny for the ALL statement
>
The hosts.deny file is only used by applications that have been compiled
to work with tcpwrappers. If you want a surefire way of blo
Hi,
I am being hit by some ips that I like to block. I like to know how can
I use hosts.deny for the ALL statement
Thanks,
Payne
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
can't you just do
100.100.100.
Ken
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Matt
> Zagrabelny
> Sent: 29 March 2006 5:41pm
> To: debian-user@lists.debian.org
> Subject: Re: hosts.deny
>
>
> On Wed, 2
On Wed, 2006-03-29 at 09:05 -0600, Jack Hale wrote:
> I am trying to block a whole subnet. (example
> 100.100.100.0-100.100.100.255).
> in my /etc/hosts.deny file I have placed this as
> 100.100.100.0/100.100.100.255.
> Is this the correct way to do this? I am using Shorewall for
Jack Hale wrote:
I am trying to block a whole subnet. (example
100.100.100.0-100.100.100.255).
in my /etc/hosts.deny file I have placed this as
100.100.100.0/100.100.100.255.
Is this the correct way to do this? I am using Shorewall for the
firewall. I am new to this. Sorry for the stupidity
I am trying to block a whole subnet. (example
100.100.100.0-100.100.100.255).
in my /etc/hosts.deny file I have placed this as
100.100.100.0/100.100.100.255.
Is this the correct way to do this? I am using Shorewall for the
firewall. I am new to this. Sorry for the stupidity.
Jack
--
To
On Mon, 17 Oct 2005 16:32:34 +0200
Nikolai Hlubek <[EMAIL PROTECTED]> wrote:
> Hi everyone :-)
>
> On one of my machines I'm running a zope server. This server should
> only be accessible from my LAN so I set:
>
> hosts.deny
> ALL: ALL
>
> The hosts.
Nikolai Hlubek wrote:
> On one of my machines I'm running a zope server. This server should only
> be accessible from my LAN so I set:
>
> hosts.deny
> ALL: ALL
...
> Ping and ssh connects are refused but the web services provided by zope
> are still accessible from the
Nikolai Hlubek napisał(a):
On one of my machines I'm running a zope server. This server should only
be accessible from my LAN so I set:
hosts.deny
ALL: ALL
The hosts.deny manual states:
This denies all service to all hosts, unless they are permitted access
by entries in the allow file.
Hello
Nikolai Hlubek (<[EMAIL PROTECTED]>) wrote:
> On one of my machines I'm running a zope server. This server should
> only be accessible from my LAN so I set:
>
> hosts.deny
> ALL: ALL
>
> The hosts.deny manual states:
> This denies all service to a
Hi everyone :-)
On one of my machines I'm running a zope server. This server should only
be accessible from my LAN so I set:
hosts.deny
ALL: ALL
The hosts.deny manual states:
This denies all service to all hosts, unless they are permitted access
by entries in the allow file.
Ping an
e windows box (lots of movie
> renders going up) are about half the speed they used to be, and am
> wondering if some of my entries in hosts.deny and .allow might be
> responsible. I followed the basics of the NFS Howto here
> http://nfs.sourceforge.net/nfs-howto/ and ended up wit
ut now I'm noticing that transfers from the windows box (lots of movie
renders going up) are about half the speed they used to be, and am
wondering if some of my entries in hosts.deny and .allow might be
responsible. I followed the basics of the NFS Howto here
http://nfs.sourceforge.net/nfs-howt
Am Mon, 2002-11-25 um 15.39 schrieb Lance Hoffmeyer:
> I have a home network and I have been having
> certain IP's probe my samba ports. I want to deny
> all access to these IP's. Would I put some sort
> of commands in my hosts.deny file? If so, what?
RTM
$ cat /
I have a home network and I have been having
certain IP's probe my samba ports. I want to deny
all access to these IP's. Would I put some sort
of commands in my hosts.deny file? If so, what?
Any other recommendations?
Lance
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
On Thu, 7 Nov 2002, Benedict Verheyen wrote:
> Hi,
>
> i have some problems setting up ssh connection (not the scope of this email though
>not yet :-) and i came across the /etc/hosts.allow & /etc/hosts.deny files.
>
> Now, i saw in some documents about ssh that they
On Thu, Nov 07, 2002 at 12:18:09PM +, Benedict Verheyen wrote:
> Now, i saw in some documents about ssh that they add "sshd: all" to the
> /etc/hosts.allow file. Am i correct that these 2 files are only used
> when you have inetd enabled and that they otherwise serve no purpose?
> So if i don't
Hi,
i have some problems setting up ssh connection (not the scope of this email though not
yet :-) and i came across the /etc/hosts.allow & /etc/hosts.deny files.
Now, i saw in some documents about ssh that they add "sshd: all" to the
/etc/hosts.allow file. Am i correct that the
Kenward Vaughan said:
I consider reinstalling the system, or can I tell how clean things
> are in some way to assess what the hell is going on?
>
if it were my system it would be a case for a reinstall. but I
would not reinstall until I was able to track down the source
of the problem(disk, contr
On Fri, Sep 20, 2002 at 09:53:49PM -0700, Eric G. Miller wrote:
> On Fri, Sep 20, 2002 at 08:41:16PM -0700, Kenward Vaughan wrote:
> > In today's system upgrade I got the following immediate message:
> >
> > ...
> > Preconfiguring packages ...
> > egrep: /et
On Fri, Sep 20, 2002 at 08:41:16PM -0700, Kenward Vaughan wrote:
> In today's system upgrade I got the following immediate message:
>
> ...
> Preconfiguring packages ...
> egrep: /etc/hosts.deny: Is a directory
> fgrep: /etc/hosts.deny: Is a directory
> ...
>
> &
In today's system upgrade I got the following immediate message:
...
Preconfiguring packages ...
egrep: /etc/hosts.deny: Is a directory
fgrep: /etc/hosts.deny: Is a directory
...
'Tis true, and at least one other /etc file is now a directory
( /etc/passwd- ).
The hosts.deny director
e log please? It might help a little bit.
>
> > I want to block this address, but I have not succeeded in configuring the
> > hosts.deny file correctly. This is what I have:
> >
> > hosts.allow: empty
> > hosts.deny:
> > ALL: 1.2.3.4
> > ALL: PARANOID
>
On Wed, Apr 25, 2001 at 09:44:00AM +0200, Sebastiaan wrote:
>
> I have reason to belive that my computer is used as a relay host for
> spam. Walking through the logs, I found one ip number which has no ip
> name, but it connects the computer every hour or so and sends some mail.
Try doing this in
On Wed, 25 Apr 2001, Hall Stevenson wrote:
> > > I use Postfix as maildaemon.
> >
> > I don't believe you want to be messing around in hosts.allow
> > for this.
Correct. Postfix does not use tcpwrappers AFAIK. Therefore, it will not
check against hosts.{allow,deny}.
> I would hope that postfix's
he logs, I found one ip number which has no ip
> > name, but it connects the computer every hour or so and sends some mail.
Logs?
Output of postconf -n?
> > I want to block this address, but I have not succeeded in configuring the
> > hosts.deny file correctly. This is what I
It might help a little bit.
> I want to block this address, but I have not succeeded in configuring the
> hosts.deny file correctly. This is what I have:
>
> hosts.allow: empty
> hosts.deny:
> ALL: 1.2.3.4
> ALL: PARANOID
>
> where 1.2.3.4 is the spammers' address.
> > I use Postfix as maildaemon.
> >
>
>
> I don't believe you want to be messing around in hosts.allow
> for this.
>
> I'm not specifically familiar with postfix, but suspect there's
> a fairly straightforward way to disable mail relays. Check
> your docs.
>
> Why do you allow them in the first p
or so and sends
> some mail.
>
>I want to block this address, but I have not succeeded in configuring
> the hosts.deny file correctly.
I think you are looking in the wrong place for a solution to your problem. You
should configure your smtp server to not allow relaying and do it quickly.
or so and sends some mail.
>
> I want to block this address, but I have not succeeded in configuring the
> hosts.deny file correctly. This is what I have:
>
> hosts.allow: empty
> hosts.deny:
> ALL: 1.2.3.4
> ALL: PARANOID
>
> where 1.2.3.4 is the spammers' addres
> > I want to block this address, but I have not succeeded in
> > > configuring the hosts.deny file correctly. This is what I have:
> > >
> > > hosts.allow: empty
> > > hosts.deny:
> > > ALL: 1.2.3.4
> > > ALL: PARANOID
> >
> >
mail.
> >
> > I want to block this address, but I have not succeeded in
> > configuring the hosts.deny file correctly. This is what I have:
> >
> > hosts.allow: empty
> > hosts.deny:
> > ALL: 1.2.3.4
> > ALL: PARANOID
>
> I believe that the ho
d in
> configuring the hosts.deny file correctly. This is what I have:
>
> hosts.allow: empty
> hosts.deny:
> ALL: 1.2.3.4
> ALL: PARANOID
I believe that the hosts.deny and hosts.allow file only control services
that are launched by the inetd daemon. It's possible that postfix
hosts.deny file correctly. This is what I have:
hosts.allow: empty
hosts.deny:
ALL: 1.2.3.4
ALL: PARANOID
where 1.2.3.4 is the spammers' address. I want to deny him smtp access (or
all access to this machine).
I tried to do this with my own ip, but I was still able to connect to port
25. Telnet a
On Tue, Apr 17, 2001 at 03:50:17PM -0500, Rich Puhek wrote:
> Will,
>
> A few questions, mostly to ask yourself, that may help you find what's
> going on.
>
> Why mess with bind on the internal machines? Why not just populate
> /etc/hosts and be done with it?
will that help win.* and mac.* machi
.lan.
(208..."?
--Rich
will trillich wrote:
>
> Apr 17 14:58:33 duo xinetd[325]: warning: /etc/hosts.deny, line 15: can't
> verify hostname: gethostbyname(kat.lan) failed
>
> aaugh!
>
> my wife's machine is windo~1 98 at 192.168.1.200; my machine is a
> mac
Apr 17 14:58:33 duo xinetd[325]: warning: /etc/hosts.deny, line 15: can't
verify hostname: gethostbyname(kat.lan) failed
aaugh!
my wife's machine is windo~1 98 at 192.168.1.200; my machine is a
mac os 8.1 at 192.168.1.100. i have no trouble connecting via ftp
(or ssh or http) but she
On Mon, 9 Apr 2001, Waldemar Brodkorb wrote:
> I think this is interesting for you, too:
> 6.1 - Known wrapper limitations
> ---
>
> Many UDP (and rpc/udp) daemons linger around for a while after they
> have serviced a request, just in case another request comes in. I
Hello Mario,
* Mario Vukelic wrote:
> On 08 Apr 2001 14:41:47 -0700, Tyrin Price wrote:
>
> > Here are some examples commented out :-)
> >
> > #:RPC: RPC based services
> > #mountd/1 dgram rpc/udp waitroot/usr/sbin/tcpd
> > /usr/sbin/rpc.mountd
> > #rstatd/1-3 dgram rpc/udp wait
On Sun, Apr 08, 2001 at 08:54:43PM +0200, Mario Vukelic wrote:
> On 08 Apr 2001 13:35:04 -0500, will trillich wrote:
>
> > # kill -HUP `pidof inetd`
> >
> > note spelling of INETD versus INITD (which i presume is a typo)
>
> Thanks for pidof. Someone should have told me that 3 yrs. ago. We
uhh.. "killall -HUP inetd" is much easier ;)
On Sun, Apr 08, 2001 at 01:35:04PM -0500, will trillich ([EMAIL PROTECTED])
wrote:
> On Sun, Apr 08, 2001 at 07:23:41PM +0200, Mario Vukelic wrote:
> > On 08 Apr 2001 19:10:42 +0200, Robert Voigt wrote:
> > > I forgot to mention that I did not forget t
On Mon, Apr 09, 2001 at 12:46:49AM +0200, Mario Vukelic wrote:
> On 08 Apr 2001 14:33:20 -0800, Ethan Benson wrote:
>
> > yes he does, portmap in debian uses tcpwrappers without being run from
> > inetd (which is impossible for portmap).
>
> Ethan Benson, you're my hero. I've been searching for
On 08 Apr 2001 14:33:20 -0800, Ethan Benson wrote:
> yes he does, portmap in debian uses tcpwrappers without being run from
> inetd (which is impossible for portmap).
Ethan Benson, you're my hero. I've been searching for this info for
hours now. All I need now is that you tell me that this ...
On Sun, Apr 08, 2001 at 01:04:26PM -0700, Tyrin Price wrote:
> * Robert Voigt <[EMAIL PROTECTED]> [08Apr01 19:07 +0200]:
> > I put the line
> > ALL: ALL
> > in /etc/hosts.deny and tried to mount a directory on this machine from
> > another one, just to see if
On 08 Apr 2001 14:41:47 -0700, Tyrin Price wrote:
> Here are some examples commented out :-)
>
> #:RPC: RPC based services
> #mountd/1 dgram rpc/udp waitroot/usr/sbin/tcpd
> /usr/sbin/rpc.mountd
> #rstatd/1-3 dgram rpc/udp waitroot/usr/sbin/tcpd
> /usr/sbin/rpc.rstatd
> #
* Mario Vukelic <[EMAIL PROTECTED]> [08Apr01 23:14 +0200]:
> Well, no. The RPC section was empty and I couldn't figure out what goes
> there. Even the new nfs howto is silent on this, although it talks a lot
> about hosts.access/deny. Frankly, I think it's stupid that debian's
> inetd.conf is nearl
On 08 Apr 2001 23:14:44 +0200, Mario Vukelic wrote:
Again replying to myself, sigh. It seems I have nowhere said that I
_can_ mount the exports.
--
I did not vote for the Austrian government
On 08 Apr 2001 14:02:52 -0700, Tyrin Price wrote:
> Do you have the RPC services enabled in your /etc/inetd.conf file? If
> so, it should be working. Make sure that the entries have no errors.
Well, no. The RPC section was empty and I couldn't figure out what goes
there. Even the new nfs howto
* Mario Vukelic <[EMAIL PROTECTED]> [08Apr01 22:35 +0200]:
> On the server I have running:
> portmap, rpc.statd, inetd, [nfsd], [lockd], [rpciod], rpc.mountd
> On the client there is running (when nfs dirs are mounted): portmap,
> rpc.statd, [lockd], [rpciod]
>
> But a tcpdchk on the server tells
share/doc/portmap/README.gz and the new HOWTO tell me to set in
/etc/hosts.allow:
portmap: my.sub.net.number/my.sub.net.mask
mountd: my.sub.net.number/my.sub.net.mask
lockd: my.sub.net.number/my.sub.net.mask
statd: my.sub.net.number/my.sub.net.mask
which I have done (I deny ALL:ALL in hosts.deny).
* Mario Vukelic <[EMAIL PROTECTED]> [08Apr01 21:49 +0200]:
> I see. But changes to (types s l o w l y) inetd.conf do require it,
> don't they?
Yes, changes to /etc/inetd.conf do not take effect until inetd is next
started, however, changes to /etc/hosts.allow and /etc/hosts
* Robert Voigt <[EMAIL PROTECTED]> [08Apr01 19:07 +0200]:
> I put the line
> ALL: ALL
> in /etc/hosts.deny and tried to mount a directory on this machine from
> another one, just to see if it actually denies access to all other hosts.
> /etc/hosts.allow is empty. But I
On 08 Apr 2001 12:42:36 -0700, Tyrin Price wrote:
> It doesn't matter, anyway, since you do not have to restart anything
> for changes to your access control files to take effect. They take
> effect immediately after a change is made.
I see. But changes to (types s l o w l y) inetd.conf do requi
* Mario Vukelic <[EMAIL PROTECTED]> [08Apr01 21:01 +0200]:
> Now it's getting lame inetd
It doesn't matter, anyway, since you do not have to restart anything
for changes to your access control files to take effect. They take
effect immediately after a change is made.
--
Regards,
-=[Ty]
On 08 Apr 2001 20:54:43 +0200, Mario Vukelic wrote:
> Yeah, and of course it's inet.d
Now it's getting lame inetd
--
I did not vote for the Austrian government
On 08 Apr 2001 13:35:04 -0500, will trillich wrote:
> # kill -HUP `pidof inetd`
>
> note spelling of INETD versus INITD (which i presume is a typo)
Thanks for pidof. Someone should have told me that 3 yrs. ago. Well, I
should've known ther must be a solution. Yeah, and of course it's inet.
On Sun, Apr 08, 2001 at 07:23:41PM +0200, Mario Vukelic wrote:
> On 08 Apr 2001 19:10:42 +0200, Robert Voigt wrote:
> > I forgot to mention that I did not forget to save the file and I rebooted
> > the
> > machine.
>
> After changes to these files you just need to do:
> ps aux|grep initd (-> get
On 08 Apr 2001 19:10:42 +0200, Robert Voigt wrote:
> I forgot to mention that I did not forget to save the file and I rebooted the
> machine.
After changes to these files you just need to do:
ps aux|grep initd (-> get the PID of initd)
kill -HUP PID-of-initd
No restart required
--
I did not v
On 08 Apr 2001 19:07:08 +0200, Robert Voigt wrote:
> I put the line
> ALL: ALL
> in /etc/hosts.deny and tried to mount a directory on this machine from
> another one, just to see if it actually denies access to all other hosts.
> /etc/hosts.allow is empty. But I could still m
On Sunday 08 April 2001 19:07, Robert Voigt wrote:
> I put the line
> ALL: ALL
> in /etc/hosts.deny and tried to mount a directory on this machine from
> another one, just to see if it actually denies access to all other hosts.
> /etc/hosts.allow is empty. But I could still mount a
I put the line
ALL: ALL
in /etc/hosts.deny and tried to mount a directory on this machine from
another one, just to see if it actually denies access to all other hosts.
/etc/hosts.allow is empty. But I could still mount and access files. What's
wrong here?
>>>>> "KMS" == Karsten M Self writes:
KMS> on Sat, Mar 24, 2001 at 04:18:09PM -0700, Mike Millner ([EMAIL
PROTECTED]) wrote:
>> When I make changes to files, for example hosts.deny or
>> hosts.access how do I get the OS to see them without r
on Sat, Mar 24, 2001 at 04:18:09PM -0700, Mike Millner ([EMAIL PROTECTED])
wrote:
> When I make changes to files, for example hosts.deny or hosts.access
> how do I get the OS to see them without rebooting? I know with my DNS
> files I can do a "rndc reload" and the changes are
ith the folowing error:
>
> Oct 30 13:09:30 garrison sshd[17223]: warning: /etc/hosts.deny, line 15:
> can't verify hostname: gethostbyname(ATHM-216-216-xxx-203.home.net) failed
> Oct 30 13:09:30 garrison sshd[17223]: refused connect from 216.216.10.203
>
> So, it seems that
On Mon, Oct 30, 2000 at 01:19:56PM -0800, Aaron Brashears wrote:
> I reconfigured sshd to have verbose logging, and tried to connect. The
> log comes back with the folowing error:
>
> Oct 30 13:09:30 garrison sshd[17223]: warning: /etc/hosts.deny, line 15:
> can&#x
and tried to connect. The
log comes back with the folowing error:
Oct 30 13:09:30 garrison sshd[17223]: warning: /etc/hosts.deny, line 15: can't
verify hostname: gethostbyname(ATHM-216-216-xxx-203.home.net) failed
Oct 30 13:09:30 garrison sshd[17223]: refused connect from 216.216.10.203
So, i
hat's going on.
> > Sep 12 01:10:32 lists sshd[1884]: refused connect from
> > 207.171.xxx.xxx
> >
> > ...and looking at /etc/hosts.deny, we find at line 15:
> >
> > ALL: PARANOID
>
> The PARANOID option forces a dns lookup on the client.
host, in /var/auth.log, I see:
>
> Sep 12 01:10:32 lists sshd[1884]: warning: /etc/hosts.deny, line 15:
> can't verify hostname: gethostbyname(140.208.171.207.in-addr.arpa)
> failed
looks like a dns problem (?)
> Sep 12 01:10:32 lists sshd[1884]: refused connect f
I've got a little problem here involving ssh, gethostbyname, and
/etc/hosts.deny, which by curious coincidence strongly resembles the
subject line of this post.
The setup: I'm connecting via ssh to a server on our DMZ, proxied
through a masquerading firewall. Like this:
1 - 100 of 145 matches
Mail list logo
