HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- tcp port used by remsh
Operating System - HP-UX
1834326
Members
2680
Online
110066
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
02-06-2003 08:55 AM
02-06-2003 08:55 AM
Hi All,
Seen a similar entry in the forum, but need clarification.
We are trying to limit the netwok services on a platform (HPUX 11.00) for security reasons.
My understanding is, for remsh (after march 2001 patching), we need to keep port 544 (kshell)open in services file. Tested it and that is ok.
Question is, kshell is hashed out in inetd.conf and hence would expect the corresponding port 544 in services file inaccessible for remsh command. But that is not the case. Also the port 544 is not LISTENING. Does the Patch (PHNE_21731) force the remsh to look at the services file as a lookup for the kshell port.
Seen a similar entry in the forum, but need clarification.
We are trying to limit the netwok services on a platform (HPUX 11.00) for security reasons.
My understanding is, for remsh (after march 2001 patching), we need to keep port 544 (kshell)open in services file. Tested it and that is ok.
Question is, kshell is hashed out in inetd.conf and hence would expect the corresponding port 544 in services file inaccessible for remsh command. But that is not the case. Also the port 544 is not LISTENING. Does the Patch (PHNE_21731) force the remsh to look at the services file as a lookup for the kshell port.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2003 09:16 AM
02-06-2003 09:16 AM
Re: tcp port used by remsh
Hi,
Think you have to take a look at tcp/514
shell 514/tcp cmd # remote command, no passwd used
kshell
kshell 544/tcp krcmd # Kerberos remote shell -kfall
Hope it helps,
Robert-Jan.
Think you have to take a look at tcp/514
shell 514/tcp cmd # remote command, no passwd used
kshell
kshell 544/tcp krcmd # Kerberos remote shell -kfall
Hope it helps,
Robert-Jan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2003 09:25 AM
02-06-2003 09:25 AM
Solution
Hi,
It looks like it does only a lookup for kshell and ekshell. As wrongly mentioned in the HP documentation, it is not looking for the ports 544 and 545 to be open.
Along with restricting the services, also use /var/adm/inetd.sec to limit the accessibility of the services that need to be open.
-Sri
It looks like it does only a lookup for kshell and ekshell. As wrongly mentioned in the HP documentation, it is not looking for the ports 544 and 545 to be open.
Along with restricting the services, also use /var/adm/inetd.sec to limit the accessibility of the services that need to be open.
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP