[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMAJcuDd26qMfYYyZ2NbpOghGYMtTN4r+JGZ1Jghxm5TmnAwYA@mail.gmail.com>
Date: Fri, 01 Apr 2016 20:28:48 +0000
From: Josiah Worcester <josiahw@...il.com>
To: musl@...ts.openwall.com
Subject: Re: AS-safe change for multithreaded setxid breaks chroot()
along with set*id()
On Fri, Apr 1, 2016 at 1:23 PM Lance Chen <cyen0312@...il.com> wrote:
> Hello there,
>
> I have been trying to run powerdns on Alpine Linux, which features musl,
> without success. It turns out that the AS-safe strategy introduced in
> the patch
>
> http://git.musl-libc.org/cgit/musl/commit/?id=78a8ef47c4d92b7680c52a85f80a81e29da86bb9
> ,
> especially the use of reading /proc/self/task, causes the failure. The
> failure condition is a combination of three features, pthread, chroot,
> and set*id. After chroot()'ing to some directory, calling set*id() will
> try to access /proc/self/task, and fail to find the directory in the new
> root. I've created a minimal POC at
> https://gist.github.com/Lance0312/c7a82793e35b322bfbdfe96b79dd3152.
>
>
A fairly simple fix for this would be to create and mount /proc in the
chroot. This is likely to be needed for some other interfaces in libc as
well as other libraries and utilities, because there's functionality of
Linux which is only really exposed in that filesystem. I don't know of
anything in particular that would fail on glibc, but I am confident that
you'll have issues, just like if you don't have /dev in the chroot.
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
