HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Inetd.sec
Operating System - HP-UX
1833324
Members
3199
Online
110051
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
09-03-2004 01:43 AM
09-03-2004 01:43 AM
We're trying to figure out if what we have is a 'bug' or not.
in the inetd.sec file we did this:
telnet allow
localhost
123.345.56.7 Dummy Host
987.87.5.322 # Dummy Ahost
584.485.5.7 Bhost Dummy\#
we were STILL able to connect to the machine from each of the dummy hosts. Theoretically, I shouldn't have been able to, right? What terminates the telnet allow in this case?
IF we move local host up to the telnet allow line, the the file works as it should.
in the inetd.sec file we did this:
telnet allow
localhost
123.345.56.7 Dummy Host
987.87.5.322 # Dummy Ahost
584.485.5.7 Bhost Dummy\#
we were STILL able to connect to the machine from each of the dummy hosts. Theoretically, I shouldn't have been able to, right? What terminates the telnet allow in this case?
IF we move local host up to the telnet allow line, the the file works as it should.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2004 01:49 AM
09-03-2004 01:49 AM
Re: Inetd.sec
Hi Danny,
Although multiple lines are "not unsupported" (from the man page), all lines but the last are ignored.
SO what you need to do is continue the line with the "\" character.
HTH,
Jeff
Although multiple lines are "not unsupported" (from the man page), all lines but the last are ignored.
SO what you need to do is continue the line with the "\" character.
HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2004 01:52 AM
09-03-2004 01:52 AM
Re: Inetd.sec
Jeff, if all lines were ignored wouldn't I have been denied access to the server? or does it not even read the telnet allow line thereby bypassing it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2004 01:58 AM
09-03-2004 01:58 AM
Solution
By default setting we can not use multiple line settins on inetd.sec file.
Your current setting is capable to allow ALL to access telnet service.
telnet allow
--> which makes to get access on telnet service.
And if you are trying comments then use as like
# Dummy Ahost
But 987.87.5.322 # Dummy Ahost will not make sense.
You have to set as,
# To allow telnet service localhost Dummy Host and Dummy Ahost Bhost Dummy
telnet allow localhost 123.345.56.7
987.87.5.322 584.485.5.7
Regards
Muthu
Your current setting is capable to allow ALL to access telnet service.
telnet allow
--> which makes to get access on telnet service.
And if you are trying comments then use as like
# Dummy Ahost
But 987.87.5.322 # Dummy Ahost will not make sense.
You have to set as,
# To allow telnet service localhost Dummy Host and Dummy Ahost Bhost Dummy
telnet allow localhost 123.345.56.7
987.87.5.322 584.485.5.7
Regards
Muthu
Easy to suggest when don't know about the problem!
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