Hello !
Sometimes when I change my /etc/hosts.allow and kill and start again
inetd, there is no difference. It's like I haven't edited
/etc/hosts.allow. If I continue making changes and stop/start inetd there
are no affections to the inetd daemons, they allow or deny as
/etc/hosts.allow isn't
Sometimes when I change my /etc/hosts.allow and kill and start again
inetd, there is no difference. It's like I haven't edited
/etc/hosts.allow. If I continue making changes and stop/start inetd there
are no affections to the inetd daemons, they allow or deny as
/etc/hosts.allow isn't
On Mon, Jun 02, 2003 at 05:26:15AM +0200, Alexander wrote:
Hello !
Sometimes when I change my /etc/hosts.allow and kill and start again
inetd, there is no difference. It's like I haven't edited
/etc/hosts.allow. If I continue making changes and stop/start inetd there
are no affections to
So what you say is that if I had opened identd socket for example then
updating /etc/hosts.allow and changing rules for ftpd won't take affect on
ftpd after new connection ? (assuming that noone is using my ftpd at all)
Thanks
On Mon, 2 Jun 2003, Matthew Seaman wrote:
On Mon, Jun 02, 2003 at
On Mon, Jun 02, 2003 at 10:46:25AM +0200, Alexander wrote:
So what you say is that if I had opened identd socket for example then
updating /etc/hosts.allow and changing rules for ftpd won't take affect on
ftpd after new connection ? (assuming that noone is using my ftpd at all)
Uh -- no. The
Hello
I really know what tcp wrappers is. I just can't exactly get your point.
I'm telling you that I shut the ftpd totaly, I've left just one line at
/etc/hosts.allow: ALL : ALL : deny
and when I simply telnet-ed my.host.com 21 it opened a connection.
I have also auth, pop3, smtp (qmail
On Mon, Jun 02, 2003 at 01:11:55PM +0200, Alexander wrote:
I really know what tcp wrappers is. I just can't exactly get your point.
I'm telling you that I shut the ftpd totaly, I've left just one line at
/etc/hosts.allow: ALL : ALL : deny
and when I simply telnet-ed my.host.com 21 it opened
