- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: inetd.sec file not working
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
01-05-2009 01:05 PM
01-05-2009 01:05 PM
work for me. What is missing?
Did a inetd -c if that is needed.
I have ip of host I am testing from and
tried with hostname also.
* deny 166.18.10.112
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2009 01:11 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2009 01:14 PM
01-05-2009 01:14 PM
Re: inetd.sec file not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2009 02:59 PM
01-05-2009 02:59 PM
Re: inetd.sec file not working
From the on-line manual:
service name { allow | deny }
{ hostaddrs | hostnames | netaddrs | netnames }
Service name is the name (not alias) of a
valid service in file /etc/services. The
service name for RPC-based services (NFS) is
the name (not alias) of a valid service in
file /etc/rpc. A service name in /etc/rpc
corresponds to a unique RPC program number.
...
The * and the - can be present in any of the
fields of the address. An address field is a
string of characters separated by a dot (.).
You cannot use wildcard for service name!
Hence, this is INVALID in /var/adm/inetd.sec:
* deny 166.18.10.112
And this is valid:
ftp deny 166.18.10.112
login deny 166.18.10.112
telnet deny 166.18.10.112
By the way, if your remote server at IP
address 166.18.10.112 has multiple network
interfaces, make sure that the way it
connects to your server with inetd.sec setup
comes through the correct interface!
Cheers,
VK2COT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2009 09:12 AM
01-06-2009 09:12 AM
Re: inetd.sec file not working
I can see that in "last -R" and "who".
This does not work with ip or hostname.
ftp deny 166.18.10.112
ftp deny jc-db-01-dm-01
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2009 10:20 AM
01-06-2009 10:20 AM
Re: inetd.sec file not working
Also, are you able to allow or deny any other services to other hosts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2009 10:28 AM
01-06-2009 10:28 AM
Re: inetd.sec file not working
tried putting just:
ftp deny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2009 10:54 AM
01-06-2009 10:54 AM
Re: inetd.sec file not working
If you are on 11.11 - Do you have this patch installed?
swlist -l product | grep -i inet:
PHNE_35017 - 1.0 inetd(1M) cumulative patch
Also, take a look at IPFilter:
http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B9901AA
You could block the host with something like this in /etc/opt/ipf/ipf.conf:
block in quick on lan0 from 166.18.10.112 to any port = 21
Assuming lan0 is you primary interface. Other than that, i'm not sure what the problem is. Your inetd.sec entry looks ok.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2009 11:30 AM
01-06-2009 11:30 AM
Re: inetd.sec file not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2009 12:46 PM
01-06-2009 12:46 PM
Re: inetd.sec file not working
Well, a nice surprise :)
I did not even suspect someone would
still use unsupported version of the O/S.
Do you have these two patches on the server?
PHNE_28312
PHNE_26828
They deal with various inetd bugs
(including inetd.sec support).
It might help.
Cheers,
VK2COT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2009 07:52 AM
01-07-2009 07:52 AM
Re: inetd.sec file not working
find any reference to PHNE_26828.
HP-UX 11.0? We are still running HP-UX 9
also, but not by choice. It's custom manufacturing
hardware/software.
There is a growing market now on old legacy
hardware/software support. HP/SUN are
loosing millions because they won't support
their own products. We even have old VAX
systems that are under support with third
party support company with ex HP/SUN/VAX
technicians that HP and SUN thought were
getting paid to much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2009 08:16 PM
01-07-2009 08:16 PM
Re: inetd.sec file not working
I understand your pain. Having
old operating systems is not pleasant
and I heard many companies believing
they were neglected by major vendors.
a) I just did a test on an HP-UX 11.00
server. I was ucky fo find one nearby.
/var/adm/inetd.sec contained:
ftp allow 192.168.30.55
It worked well. This is the syslog entry:
Jan 8 15:09:06 myhost inetd[3688]: ftp/tcp: Connection from myhost2 (192.168.30.55) at Thu Jan 8 15:09:06 2009
Jan 8 15:09:08 vmyhost ftpd[3688]: USER dusan
Jan 8 15:09:08 myhost ftpd[3688]: PASS password
And when I disabled ftp services in /var/adm/inetd.sec:
ftp deny
or
ftp deny 192.168.30.55
... I got correct response from the server:
Jan 8 15:06:04 myhost inetd[885]: ftp/tcp: Access denied for myhost2 (192.168.30.55) at Thu Jan 8 15:06:04 2009
Jan 8 15:05:35 myhost inetd[885]: ident/tcp: Exit status 1
I am not really sure why you are having problems.
It works fine on HP-UX 11.00.
What do you syslog entries show?
Cheers,
VK2COT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2009 02:46 PM
01-08-2009 02:46 PM
Re: inetd.sec file not working
1. You cannot have just a hostname if the
host is in another domain. Even if it
is aliased in DNS as being in the same
domain it will not work.
It has to be what it is connecting as.
Just hostname will work if both hosts
are in the same domain. IP will always
work. Better to use IP.
I had tried FQHN but number two below
was breaking it.
2. You cannot have multiple server entries.
e.g.
ftp deny
ftp deny
The last one will override the first
ones.
I had another ftp entry farther down in the
file that was overriding the first ftp entry.
There is no need to do an inetd -c.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2009 02:57 PM
01-08-2009 02:57 PM
Re: inetd.sec file not working
install TCPwrappers or other.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2009 04:57 PM
01-08-2009 04:57 PM
Re: inetd.sec file not working
You should have told us earlier :)
Here is the excerpt from inetd.sec(4)
on-line manual:
"Multiple allow|deny lines for each service are not unsupported. If there are multiple allow|deny lines for a particular service, all but the last line are ignored."
I think we all deserve some points from you
before you close the thread :)
Cheers,
VK2COT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2009 06:56 PM
01-08-2009 06:56 PM
Re: inetd.sec file not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2009 04:35 PM
01-09-2009 04:35 PM
Re: inetd.sec file not working
Your problem gave me an idea. Why not
automate this check? So, I updated my own
Perl script for Operations Acceptance
Testing and Auditing of HP-UX servers:
http://www.circlingcycle.com.au/Unix-sources/HP-UX-check-OAT.pl.txt
It will, among the other things, report:
AUDIT-PASS: Inetd managed through ACLs (/var/adm/inetd.sec used)
AUDIT-NOTE: Multiple allow or deny lines for each service are not unsupported.
AUDIT-NOTE: If there are multiple allow or deny lines for a particular service,
AUDIT-NOTE: all but the last line are ignored
AUDIT-INFO: Active services in /var/adm/inetd.sec
ftp 192.168.40.30
telnet
shell deny
ftp 10.15.20.30 172.16.1.4
AUDIT-WARN: Entry for service "ftp" exists more than once in /var/adm/inetd.sec
Thanks for giving me an idea :)
Cheers,
VK2COT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2009 04:42 PM
01-09-2009 04:42 PM
Re: inetd.sec file not working
I just realised: there is an error in
language style. It is actually wrong in
HP-UX on-line manual for inetd.sec:
QUOTE
Multiple allow|deny lines for each service are not unsupported.
END QUOTE
It should state:
"Multiple allow|deny lines for each service are not supported."
or even:
"Multiple allow|deny lines for each service are unsupported."
I made a change in my Perl script too.
Cheers,
VK2COT