On Tuesday, September 16, 2014 12:42:36 PM Mateusz Guzik wrote:
> On Fri, Sep 12, 2014 at 09:29:56PM -0700, Peter Wemm wrote:
> > On Thursday, September 11, 2014 12:38:02 PM Patrick Kelsey wrote:
> > > On Wed, Sep 10, 2014 at 3:00 AM, Andrey Chernov
wrote:
> > > > On 09.09.2014 21:53, Patrick Kel
On Fri, Sep 12, 2014 at 09:29:56PM -0700, Peter Wemm wrote:
> On Thursday, September 11, 2014 12:38:02 PM Patrick Kelsey wrote:
> > On Wed, Sep 10, 2014 at 3:00 AM, Andrey Chernov wrote:
> > > On 09.09.2014 21:53, Patrick Kelsey wrote:
> > > > I don't think it is worth the trouble, as given the la
On 13.09.2014 8:29, Peter Wemm wrote:
> On Thursday, September 11, 2014 12:38:02 PM Patrick Kelsey wrote:
>> On Wed, Sep 10, 2014 at 3:00 AM, Andrey Chernov wrote:
>>> On 09.09.2014 21:53, Patrick Kelsey wrote:
I don't think it is worth the trouble, as given the larger pattern of
libc ro
On Thursday, September 11, 2014 12:38:02 PM Patrick Kelsey wrote:
> On Wed, Sep 10, 2014 at 3:00 AM, Andrey Chernov wrote:
> > On 09.09.2014 21:53, Patrick Kelsey wrote:
> > > I don't think it is worth the trouble, as given the larger pattern of
> > > libc routines requiring multiple capsicum righ
On Wed, Sep 10, 2014 at 3:00 AM, Andrey Chernov wrote:
> On 09.09.2014 21:53, Patrick Kelsey wrote:
> > I don't think it is worth the trouble, as given the larger pattern of
> > libc routines requiring multiple capsicum rights, it seems one will in
> > general have to have libc implementation kno
On 09.09.2014 21:53, Patrick Kelsey wrote:
> I don't think it is worth the trouble, as given the larger pattern of
> libc routines requiring multiple capsicum rights, it seems one will in
> general have to have libc implementation knowledge when using it in
> concert with capsicum. For example, co
On Mon, Sep 8, 2014 at 6:00 PM, Andrey Chernov wrote:
> On 09.09.2014 1:13, Patrick Kelsey wrote:
> > You make a godo point about the wider use of fcntl() in libc - aside
> > from the rpc code, by my count there are 14 other entry points in libc
> > that use fcntl in their implementation. To exp
On 09.09.2014 1:13, Patrick Kelsey wrote:
> You make a godo point about the wider use of fcntl() in libc - aside
> from the rpc code, by my count there are 14 other entry points in libc
> that use fcntl in their implementation. To experience breakage,
> programs that use those entry points would a
On Mon, Sep 8, 2014 at 4:42 PM, Andrey Chernov wrote:
> On 09.09.2014 0:28, Patrick Kelsey wrote:
> > In r268997, _ftello() was modified to use _fcntl(F_GETFL) in the
> > non-append, write-only path. Consequently, programs that use _ftello()
> > (via ftell, fgetpos, fsetpos, fseek, rewind...) on
On 09.09.2014 0:28, Patrick Kelsey wrote:
> In r268997, _ftello() was modified to use _fcntl(F_GETFL) in the
> non-append, write-only path. Consequently, programs that use _ftello()
> (via ftell, fgetpos, fsetpos, fseek, rewind...) on non-append,
> write-only files and that use capsicum to restric
In r268997, _ftello() was modified to use _fcntl(F_GETFL) in the
non-append, write-only path. Consequently, programs that use _ftello()
(via ftell, fgetpos, fsetpos, fseek, rewind...) on non-append, write-only
files and that use capsicum to restrict capabilities on the associated fds
to [CAP_SEEK,
11 matches
Mail list logo
