#2 bug in trustees 2.10 when running as root

closed-fixed
nobody
None
5
2005-02-12
2003-11-12
Anonymous
No

Hi, I'm testing out your project (which looks very
nice, btw), and I
encountered a minor bug. Hopefully this is the right
place to submit this...

Here's the problem... If I run a script like the
following as root:

if [ -x /tmp/filename ]; then echo executable; fi

It will always echo "executable" regardless of whether
/tmp/filename
is actually executable or not. However, this problem
only appears if
I do this as root. If I do it as a normal user,
there's no problem.

Running 'text -x' has similar results. A random sample
of other test
options seem to be correct (as compared to a
non-trustee'd kernel),
such as -L, -r, -w, -d.

According to strace, 'text -x' makes use of an fstat64
call, then
a stat64 call.

I'm using stock kernel 2.4.20 with your
trustees.2.10-2.4.20-patch on
a RedHat 7.3 system. And I am using a blank
/etc/trustee.conf file,
so everything should be defaulting to standard Unix
permissions. The
'ls' program does report correct permissions and
execute status on all
files, however.

- Danny Sung <dannys@changind.com>

Discussion

  • Andrew Ruder
    Andrew Ruder
    2005-02-12

    Logged In: YES
    user_id=549930

    This is fixed in subversion of the 2.6 port of trustees.
    Sorry it took so long to get to it. (Project under new
    management ;)

     
  • Andrew Ruder
    Andrew Ruder
    2005-02-12

    • status: open --> closed-fixed