Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Sun
[Top] [All Lists]

Re: chroot of iPlanet 6.0 and Siebel....

Subject: Re: chroot of iPlanet 6.0 and Siebel....
Date: Tue, 31 May 2005 09:38:35 -0700 (PDT)
Lo, Jonathan Katz and the teakettle whistled in unison:

All,

I'm attempting to establish a chrooted environment for an iPlanet
6.0SP9 webserver with Siebel web extensions installed for our
enterprise on Solaris 9. I've been able to operate the SSL-based
webserver in the chrooted environment with no major problems. However,
when I enable the Siebel web extensions the webserver fails to start;
I'm not even prompted for the SSL password upon start, the webserver
coredumps. Based on error messages it looks like I'm missing
libraries, but after examining LD_LIBRARY_PATH and judicious use of
ldd I'm coming up short...
[snip]

I'm afraid I can't help with the specifics of this one, but one
approach I've tried with some success when I've had really peculiar
run time problems is using truss to find out what system calls the
errant program is making and what it's getting out of them.  That
sometimes uncovers file open failures that I'd never find otherwise or
similar odd problems.

You might want to try 'pldd' on a system where the application is
running correctly (not in a chroot)  'pldd' will give you not only
the directly required libraries, like 'ldd' will, but it also lists
any librarires which those libraries call. That should give you all
of the dependencies (library-wise at least)

HTH,

Warren

<Prev in Thread] Current Thread [Next in Thread>