Re: Documenting a server conf
- From: Dave Hinz <DaveHinz@xxxxxxxxx>
- Date: 24 Oct 2007 03:47:01 GMT
On Mon, 22 Oct 2007 12:48:11 -0000, edcrosbys <edcrosbys@xxxxxxxxx> wrote:
I'll give it a shake..
Situation:
Server doesn't have network connectivity and I cannot get root access.
A vague situation description, I'll admit, yes.
Assumptions:
no root console access due to incorrect passwd
something is running that will be corrupted if we bounce and force our
way in via single user.
oooh, a nice twist, thank you; I may use that.
domainname was mentioned sounds like sweet sweet insecurity to me.
Oh, hell yes.
The co-workers can provide little assistance (in the way of user level
acct only)
Query users/bosses/others for any admin type access - probably futile,
but could pay off
Nice approach.
Hop on a functioning box as user and grab NIS map. Run NIS map (edited
for user security, of course) through jack the ripper.
While Jack is running, hop on dead box as user.
Look at network config, log files, GSM hardware logs, sudo config
(pray some more), others with uid 0, are there apps that prevent
forced access.
In other words, bad security practices are out there, see if any of 'em
are in place here you can exploit. Hell, if we had NIS, we could create
a (mumble) with a UID of (grumblesnarf) and be in.
Have network guy check things from his end just in case.
If everything appears to be configured correctly and you see no
errors, replace the cable.
Stranger things have happened.
Check for SUID/SGID files
If everything is properly secured (except using NIS) and the issue is
a config/hardware problem on the server, then you will need to bring
the box down to gain access and/or fix hardware. Now if my assumptions
were off, you have a different ball game.
Thank you, I enjoyed the exercise
You gave me a couple ideas that I haven't used. If the box is off the
network and deemed dead enough to call dead, options then include trying
to boot from alternate media (cd, boot net:dhcp - s , or probably other
ways), or the ultimate brute force, take the HD out and stick it in a
box you HAVE root on.
With physical access, logical access is just a matter of time. The most
fascinating thing I ever watched was one of the guys who at the time
worked for me, break into a box by dropping to the OK prompt and poking
around in the memory, changing the effective UID of the running process
to 0, and then typing "go" at the OK prompt to get back into his (now,
root) shell. Amazing.
.
- Follow-Ups:
- Re: Documenting a server conf
- From: Frank Cusack
- Re: Documenting a server conf
- References:
- Documenting a server conf
- From: andrea
- Re: Documenting a server conf
- From: Michaël Grünewald
- Re: Documenting a server conf
- From: Thorbjoern Ravn Andersen
- Re: Documenting a server conf
- From: andrea
- Re: Documenting a server conf
- From: Thorbjoern Ravn Andersen
- Re: Documenting a server conf
- From: Doug Freyburger
- Re: Documenting a server conf
- From: Dave Hinz
- Re: Documenting a server conf
- From: Thorbjoern Ravn Andersen
- Re: Documenting a server conf
- From: Dave Hinz
- Re: Documenting a server conf
- From: Thorbjoern Ravn Andersen
- Re: Documenting a server conf
- From: edcrosbys
- Documenting a server conf
- Prev by Date: Re: Aix Remote Print Queues
- Next by Date: Re: Documenting a server conf
- Previous by thread: Re: Documenting a server conf
- Next by thread: Re: Documenting a server conf
- Index(es):
Relevant Pages
|
Loading