inetd.sec

[Darrell Allen]

Hi everyone,

I thought inetd.sec was only used to restrict access from remote systems to the local system's services. The man page doesn't indicate otherwise.

Has anyone actually used inetd.sec to disable connections being initiated from the local system?

I see how you could deny something like ftp from the local server to itself but that's still blocking it from the server side.

Thanks,
Darrell

[harry d brown jr · Accepted solution]

inetd.sec is for incoming not outgoing requests!

To stop people from using something like ftp or telnet to another machine, simply change the permissions or "group it".

live free or die
harry

[Uday_S_Ankolekar]

Hi,

This file is to stop telnet ,ftp,rlogin etc from the other boxes. You can configure it to disable incomming requests.

-USA..

[Craig Rants]

If you want to totally block telnet or ftp services, comment out the service in the inetd.conf.

Then run inetd -c

Good Luck,
C

[Roger Baptiste]

<>

You are right. inetd.sec blocks incoming connections from external systems.

<>

oh yes, i just tried it ;-)
just add the line
telnet deny
It works. But it holds no meaning. Since, why would i need to stop telnetting into a system from that system iteslf?



when you do telnet , ftp ..
it tries to open a port of that service at the remote server. At the remote server, the inetd daemon services the request. Before the request is serviced, it checks whether it is authorised connection by looking the inetd.sec file.
If from systemA you do telnet to systemA , the local system will also be the remote server!

HTH
raj

[James Beamish-White]

Definitely only incoming.... from the man page:

"When inetd accepts a connection from a remote system..."

Other unix flavours need to use tcpwrappers to do the same thing, but HP is sooo good to us we don't need it ;-)

For outgoing (as noted in another thread in the forum), it's removal of access priveleges (chmod 500) that limit outgoing on a box, or firewalls if limiting at a network level.

Cheers,
James

[Darrell Allen]

Thanks everyone.

So far I've heard nothing different from what I thought: inted.sec is only for incoming connections (server side, that is).

Raj, in reference to disabling connections initiated from the local system, would you expand on what you mean when you say it works but it holds no meaning? I poorly worded the question before. To be specific, can inetd.sec be used to deny a user on the same box from initiating a connection as a client to another host? I think you're saying no which is what I believe to be true as well.

Darrell

[Sanjay_6]

Hi Darrell,

As other have already said, inetd.sec is to restrict/prevent access to your system, not from your system.

Hope this helps.

Regds

[Darrell Allen]

Thanks for confirming my understanding of this issue.

Darrell