Re: {bb} OpenBSD chroot Apache and History...

[Philip Clark <pcclark@tiscali.co.uk>]

Oooooo, nasty :)

I'm going to assume that you have all the necessary binaries,
libraries and configuration files copied into the jail and
have no problem running a representative sample of lines
from the standard scripts from the command line (as the
BB user).

Two things then spring to mind. First, can you append to
the dev/null inside the jail? In other words, will:

  echo "nonsense" >> /dev/null

work, where:

  echo "nonsense" > /dev/null

will not?

Second, what are the permissions on the jailed "dev" directory?
Does making it world writable help?

Cheers, Phil.



On Thu, 2004-10-28 at 18:56, Ed Vazquez wrote:
> I searched the archives and didn't come up with anything 
> relevant.
> 
> Has anyone gotten the history portion to work when riding on 
> OpenBSD and using the built-in chroot'd version of Apache?
> 
> I keep getting:
> 
> /cgi-bin/bb-hist.sh: /bb/bb/etc/bbinc.sh[55]: cannot create 
> /dev/null: Device not configured
> /cgi-bin/bb-hist.sh[579]: cannot create /dev/null: Device not 
> configured
> [Thu Oct 28 11:51:15 2004] [error] [client 10.27.0.67] 
> Premature end of script headers: /cgi-bin/bb-hist.sh
> 
> And yet I specifically created a chroot /dev/null device that 
> shows up as:
> 
> # file /var/www/dev/null
> dev/null: character special (2/2)
> 
> which to me is identical to:
> 
> # file /dev/null
> /dev/null: character special (2/2)
> 
> And has the same permissions:
> 
> # ls -l /var/www/dev/null
> crw-rw-rw-  1 root  wheel    2,   2 Oct 12 12:32 dev/null
> 
> as the main file:
> 
> # ls -l /dev/null
> crw-rw-rw-  1 root  wheel    2,   2 Oct 28 01:29 /dev/null
> 
> Everything else seems to be perking right along.
> 
> Thanks in advance!
> 
> --
> Ed V.


-- 
Beware of Programmers who carry screwdrivers. (Leonard Brandwein)

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.