grsecurity forums

Hi!

First:

Let's say i have this user (xpto) belonging to this group (users).
I also have a user role for xpto and a group role for users.
Is xpto affected by both roles or just the user role?

Second:

Considering this acl:

/usr/bin
/usr/bin/*

A 'ls' on /usr/bin shows lots of symlinks, which obviously don't work, but it shows the "physical" presence of real files. Can this be prevented?

Using 2.0pre3

Thanks in advance

The role lookups first try to find a user role, then a group role, then use the default role. Thus, in your case, it's the user role that matters.

I'm not sure I understand your second question. Do you want to hide what's in /usr/bin?

-Brad

I gave /usr/bin as an example.

I undestand that symlinks show up if u give read permission for the real file, but i see symlinks that, as far as i can tell, have no relation with files i've given permission to be seen.

There's a problem with globbing and symlinks. I'm working on fixing it right now.

-Brad

It's fixed in current CVS. The bug in gradm wasn't present in 1.9.9*. It was a stat/lstat typo.
Thanks for pointing it out

-Brad

Great!

And it is I who thanks