Operating System - HP-UX
1752598 Members
5503 Online
108788 Solutions
New Discussion юеВ

Re: inetd.sec: Why user still able to TELNET

 
Jose Mosquera
Honored Contributor

Re: inetd.sec: Why user still able to TELNET

Hi Shukor,

Have you made the single and full IP address test? Does Works?

In any case I've observe that PHNE_35017 have been superseded by PHNE_36202 resolving a lot of critical failures. Please check on:
http://www11.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_36202&sel={hpux:11.11,}&BC=main|search|

As you will see the new patch do not have patch dependencies.

Rgds.
nijokj
Trusted Contributor

Re: inetd.sec: Why user still able to TELNET

Hi,
In case allow is there system will allow only those IP to telnet to this system, remaining IPs denid by d├Г┬иfaut, Can you post your inetd.conf whole entries.
ManojK_1
Valued Contributor

Re: inetd.sec: Why user still able to TELNET

Hi Shukur,

Can you please confirm that all these logins are through telnet.

Kill the logins from segment 23.148.2.0 and append the following entry in
/var/adm/inetd.sec and verify.

telnet deny 23.148.2.1-254



Manoj K
Thanks and Regards,
Manoj K
Shukor
Frequent Advisor

Re: inetd.sec: Why user still able to TELNET

Hi,

I've removed all entry for telnet allow because too many and getting user to test again. Locally tested and it's worked (specified IP Address). Will update and assign point once Korea's user responded.



Shukor
Frequent Advisor

Re: inetd.sec: Why user still able to TELNET

SOLUTION: Remove "telnet allow" portion and retain only "telnet deny" (telnet deny 23.148) in inetd.sec.

From the solution above, maybe I could say..don't put "telnet allow" and "telnet deny" together in inet.sec file.

Thanks everyone!! :)

Shukor