>1. Dissasociate from the controlling terminal. (2 * fork)
No problem. fork()
>2. Close *ALL* open handles. (call to sysopt, multiple calls to close)
No problem. close()
>3. Destroy the runtime environment && Re-create what is needed.
> (To stop bad/unwanted environment vars being passed to called
> programs - namely the virus scanners.)
No problem. Modify %ENV
>4. Open a channel to Syslog.
No problem. open()
>5. SU to a non-privileged user.
No problem. Set $UID
>6. chroot with a minimal runtime environment.
No problem. chroot()
>The problem here being a complete perl runtime would be needed in the
>chroot environment. As the entire purpose of a chroot prison is to
>provide a restrictive environment without any of the tools a hacker would
>find useful - this defeats the purpose of it.
Depends on what you need at runtime. Perl gets compiled first and then
interpreted so it doesn't need to read any modules after compilation.
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
