Mail Archives: cygwin/2002/07/03/15:52:34
Hello Corinna,
Wednesday, July 03, 2002, 8:56:52 PM, you wrote:
CV> On Wed, Jul 03, 2002 at 01:39:50PM -0400, Jon LaBadie wrote:
>> On Wed, Jul 03, 2002 at 07:26:02PM +0200, Pavel Tsekov wrote:
>> > Oh, boy! I mistyped the subject in the original mail :( It sounds so
>> > silly, that I doubt anyone have red it at all...
>>
>> Failed for me which is correct behavior.
CV> Yep, for me, too. Pavel, you should check the *whole* ACL using
CV> getfacl.
Thanks, for reminding me of that tool! I've tried to use cacls but the
information wasn't so usefull as the output of getfacl :)
It seems that I was too fast to send the report - cygwin1.dll seems to
perform fine... in normal situations i.e.:
mkdir somedir
chmod 600 somedir
cd somdir -> Permission denied
The problem is, as it seems, with directories created from setup.exe,
since these are created to be accessible for everyone.
Here is the output of getfacl on /usr/src:
paveltz AT MORDOR /usr
$ getfacl.exe src
# file: src
# owner: paveltz
# group: Nessuno
user::---
group::---
group:SYSTEM:rwx
group:Administrators:rwx
group:Users:rwx
mask::---
other::---
default:user::---
default:group::---
default:group:Everyone:---
default:group:SYSTEM:---
default:group:Administrators:---
default:group:Users:-w-
default:mask::---
default:other::---
While on directories created with, say, mkdir, the output looks like
this:
paveltz AT MORDOR /usr
$ getfacl.exe bbb
# file: bbb
# owner: paveltz
# group: Nessuno
user::---
group::---
mask::---
other::---
default:user::---
default:group::---
default:mask::---
default:other::---
Both /usr/src and /usr/bbb have been chmod-ed to mode 000 before
executing getfacl.exe.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -