[lkml]   [2004]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: setpeuid(pid_t, uid_t) proposal
    On Mon, 23 Aug 2004 23:50:05 CDT, Jerry Haltom said:

    > Apache runs as a low privledge user, but can obtain the permissions of
    > the user that requested the service. Apache can't give itself access, so
    > it relies on a seperate process to do so. A request is received to
    > Apache. The request comes with authentication information (in a number
    > of forms, Basic, Kerberos (GSSAPI), CRAM, NTLM, whatever). The
    > authentication information is received by the Apache module that handles
    > the specific authentication type. This module passes the security
    > information to a seperate stand alone daemon, which is running as root.
    > This daemon is highly audited and does one purpose, and does it well.

    What does this buy you that having the separate daemon just do
    a fork/seteuid/exec to do the work, and passing the results back via a
    Unix socket or shared mem or what-have-you?

    Alternatively, what would this give you that isn't already done by
    the SELinux support for cron, or Apache suexec, which already allow
    "run the following in another context" functionality?
    [unhandled content-type:application/pgp-signature]
     \ /
      Last update: 2005-03-22 14:05    [W:0.019 / U:54.392 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site