- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: inetd.sec
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2005 02:36 PM
12-15-2005 02:36 PM
I want to make sure I have secured inetd.conf as it should be. I am running a MCSG environment and have found that we should have a inetd.sec file to secure the identd service. What should this file contain? Thanks for your help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2005 02:44 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2005 03:06 PM
12-15-2005 03:06 PM
Re: inetd.sec
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2005 03:40 PM
12-15-2005 03:40 PM
Re: inetd.sec
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2005 03:49 PM
12-15-2005 03:49 PM
Re: inetd.sec
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2005 08:32 PM
12-15-2005 08:32 PM
Re: inetd.sec
you can restrict the inetd services.
edit the /var/adm/inetd.sec
if u want to allow telnet only to a specific ip or network, put
telnetd allow (ipaddress or hostname )
iam not aware of identd service .
if it is there you can restrict the service like this.
identd allow 10.0.0.02
identd deny 10.0.0.25
...................
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2005 08:50 PM
12-15-2005 08:50 PM
Re: inetd.sec
servicename allow/deny ip-address/network/hostname
and save it.
You can get sample file as,
/usr/newconfig/var/adm/inetd.sec
use that and try it out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2005 02:07 AM
12-16-2005 02:07 AM
Re: inetd.sec
ident 113/tcp authentication # RFC1413
No, I am not getting any messages in syslog for ident.
I also just downloaded the latest PDF of "Managing Serviceguard, 12th Edition, October 2005" and searched for ident in it. There is mention of it on page 194, but our cluster was not set up like they say it should be to not use identd and it is still running fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2005 08:44 AM
12-16-2005 08:44 AM
Re: inetd.sec
From: http://docs.hp.com/en/B3936-90079/ch05s01.html
Username Validation
Serviceguard relies on the ident service of the client node to verify the username of the incoming network connection. If the Serviceguard daemon is unable to connect to the client's ident daemon, permission will be denied.
Root on a node is defined as any user who has the UID of 0. For a user to be identified as root on a remote system, the "root" user entry in /etc/passwd for the local system must come before any other user who may also be UID 0. The ident daemon will return the username for the first UID match. For Serviceguard to consider a remote user as a root user on that remote node, the ident service must return the username as "root".
It is possible to configure Serviceguard to not use the ident service, however this configuration is not recommended. Consult the whitepaper "Securing Serviceguard" for more information.
To disable the use of identd, add the -i option to the tcp hacl-cfg and hacl-probe inetd configurations.
For example, on HP-UX with Serviceguard A.11.16
1.
Change the cmclconfd entry in /etc/inetd.conf to appear as: hacl-cfg stream tcp nowait root /usr/lbin/cmclconfd \ cmclconfd -c -i.
2.
Change the cmomd entry in /etc/inetd.conf to appear as: hacl-probe stream tcp nowait root \ /opt/cmom/lbin/cmomd /opt/cmom/lbin/cmomd -i -f \ /var/opt/cmom/cmomd.log -r /var/opt/cmom.
3.
Restart inetd: /etc/init.d/inetd restart.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2005 12:39 PM
12-16-2005 12:39 PM
Re: inetd.sec
Are the backward slashs (\)suppose to be part of the hacl entries in /etc/inetd.conf? When I put them in and restart inetd, I get a message in my syslog stating an unexpected \ was encountered.
Also, the reason for this line of questioning is because we are getting the following message in our syslog that I can't seem to correct:
Dec 16 20:39:13 cmclconfd[12182]: cmclconfd running with weak security (id
entd disabled)
This message repeats several times a minute. How can I correct this?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2005 02:44 PM
12-16-2005 02:44 PM
Re: inetd.sec
As mentioned in the SG manual , bypassing the "identd" is not recommended.
Refer follwing HP doc and ensure the compliance mentioned therein.
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000081786362