On Fri, 2013-10-18 at 08:29 -0400, krishna e bera wrote:
> Problem: does "chroot" mean anything in a Windows environment?
There is no real chroot solution on windows that I know of. What exist
is an application virtualisation (which of course has other targets) but
I would say that it also includ
On 13-10-18 03:34 AM, Fabio Pietrosanti (naif) wrote:
> I think that Tor should implement natively support for self-chrooting
> and that those kind of approach are dirty, unmaintainable, hacks.
>
> Most security software does support chrooting natively, simply by
> opening the relevant filesystem
I think that Tor should implement natively support for self-chrooting
and that those kind of approach are dirty, unmaintainable, hacks.
Most security software does support chrooting natively, simply by
opening the relevant filesystem filedescriptor before chrooting, and
then operating over it from
At 23:13 10/16/2013 -0400, starlight.201...@binnacle.cx wrote:
>Newer versions of 'openssl' require access to
>
> /proc/sys/kernel/random
>
Got this wrong, in part due to the difficulty
of debugging 'chroot'.
'libevent' does make use of /proc/sys/kernel/random/uuid
if it's available but toler
At 23:13 10/16/2013 -0400, starlight.201...@binnacle.cx wrote:
>Newer versions of 'openssl' require access to
With the assistance of 'strings'
it was determined that it is
/usr/local/lib64/libevent-2.0.so.5.1.9
that is actually responsible for accessing
/proc/sys/kernel/random/uuid
durin
Newer versions of 'openssl' require access to
/proc/sys/kernel/random
and so the line
/proc/sys/kernel/random /chroot_tor/proc/sys/kernel/random auto bind 0 0
must be added to the
/etc/fstab
file or the command
mount -o bind /proc/sys/kernel/random /chroot_tor/proc/sys/kernel/ra
