Danek Duvall wrote at Tue Jul 21 2009 16:48:53 GMT-0700 (PDT):
> On Tue, Jul 21, 2009 at 04:41:00PM -0700, James Walker wrote:
>
>> Exported Interfaces  Classification  Comment
>> ===================  ==============  ===================
>> SUNWfakeroot         Uncommitted     Package
>>
>> /usr/bin/fakeroot    Uncommitted     Command
>> /usr/bin/faked               Uncommitted     Daemon
>
> Is there any point in running the daemon by hand, or should that be a
> Private interface, stuck off in /usr/lib?

The daemon can be run by hand, but it would be pointless.
Running faked is only useful if there's a fakeroot at the
other end telling it what to fake.

>> Imported Interfaces  Classification  Comment
>> ===================  ==============  ===========================
>> SUNWlibms            Committed       Math&  Microtasking Libraries (Usr)
>
> What math functions does this use?

None, really.

>> Project Private
>> ===============
>> /usr/lib/libfakeroot.so.0    Library
>> /usr/lib/libfakeroot.so              Symbolic link
>> /usr/lib/64/libfakeroot.so.0 library (64bit)
>> /usr/lib/64/libfakeroot.so   Symbolic link (64bit)
>
> If these are project private, why have compilation symlinks?

fakeroot ld_preloads libfakeroot.so to achieve its desired end.
Presumably this is for future "expansion"; should there be another
version of the library in a future release, say, libfakeroot.so.1,
fakeroot can continue to ld_preload libfakeroot.so as it does now.

> Has any thought been given to having fake elevated privileges, or fake role
> assumption?

Apologies: I am a bit unsure as to the meaning of the question.

If you are asking whether fakeroot can cause privilege escalation
or allow the user to assume roles s/he is not allowed to assume,
then the answer is it cannot.

If, OTOH, your question is whether fakeroot can give the impression
of privilege escalation, then yes, that's what it is basically
designed for.  When a user runs (a command under) fakeroot, s/he
is fakely reported (to the command) as being root.  So, the command
thinks the user has all privileges.

There's also some text about this included in the proposal and the
manual pages.

-Ravindra.

Reply via email to