Reading the security document for CMS 16 it seems to state that restricting access to telnet and only allowing users to access the server using ssh is as easy as:
"On the CMS server, you can restrict the telnet service to the local host using the following
restrictions:
● /etc/hosts.allow
in.telnetd : localhost # allow telnet only from within the server
● /etc/hosts.deny
in.telnetd: ALL # deny all telnet except as specified in hosts.allow"
Avaya on the other hand is telling my co-worker this is not the case and it's more difficult than this. I almost think that Avaya just want the money for doing the work. Thougts, comments, corrections, steps to actually restrict telnet?
Thanks.
- Stinney
"Scire ubi aliquid invenire possis, ea demum maxima pars eruditionis est"
"To know where to find anything is, after all, the greatest part of education"
"On the CMS server, you can restrict the telnet service to the local host using the following
restrictions:
● /etc/hosts.allow
in.telnetd : localhost # allow telnet only from within the server
● /etc/hosts.deny
in.telnetd: ALL # deny all telnet except as specified in hosts.allow"
Avaya on the other hand is telling my co-worker this is not the case and it's more difficult than this. I almost think that Avaya just want the money for doing the work. Thougts, comments, corrections, steps to actually restrict telnet?
Thanks.
- Stinney
"Scire ubi aliquid invenire possis, ea demum maxima pars eruditionis est"
"To know where to find anything is, after all, the greatest part of education"