Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 63408 - the X-permission doesn't work recursive with setfacl in acl-2.2.13-r2
Summary: the X-permission doesn't work recursive with setfacl in acl-2.2.13-r2
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-09 04:41 UTC by b52
Modified: 2005-05-01 03:24 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description b52 2004-09-09 04:41:08 UTC
Hi,
i found out that the X-permission doesn't work recursive with setfacl in acl-2.2.13-r2.
X means: execute only if the file is a directory or already has execute permission for some user

An Example:

asterix dir # getfacl file 
# file: file
# owner: root
# group: root
user::rw-
group::r--
other::r--

asterix dir # setfacl -Rm u:user:r-X .

asterix dir # getfacl file
# file: file
# owner: root
# group: root
user::rw-
user:user:r-x
group::r--
mask::r-x
other::r--

Why does this file now have execute permissions??
The X flag should not change the exexute permissions of this file, because its neither a directory nor did it have the execute permission.

If I do "setfacl -m u:user:r-X file" the X flag works correct and the file has no execute permissions after that.

I need to change a lot of permissions recursivly, so this bug realy troubling.
Thanks, bye, b52

Reproducible: Always
Steps to Reproduce:
1. compare "setfacl -m u:user:r-X file" and "setfacl -Rm u:user:r-X ."
2.
3.

Actual Results:  
false permissions set

Expected Results:  
correct permissions set

Portage 2.0.50-r10 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.3.20040420-r1,
2.6.8-gentoo-r3)
=================================================================
System uname: 2.6.8-gentoo-r3 i686 AMD Duron(tm) processor
Gentoo Base System version 1.4.16
distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-mcpu=athlon -mmmx -m3dnow -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-mcpu=athlon -mmmx -m3dnow -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distcc fixpackages sandbox"
GENTOO_MIRRORS="http://gentoo.inode.at ftp://gentoo.inode.at/source
ftp://ftp.tu-clausthal.de/pub/linux/gentoo/
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/
ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/
rsync://linux.rz.ruhr-uni-bochum.de/gentoo/
http://ftp.uni-erlangen.de/pub/mirrors/gentoo
ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo
ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo
rsync://ftp.join.uni-muenster.de/gentoo/"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X509 acl acpi acpi4linux activefilter amd apache2 autofs berkdb
bluetooth cdr cgi clamav crypt cups drac ethereal fastcgi fax foomaticdb freetds
fullrpc gdbm gif gpm imap innodb ipalias ipv6 isdn jpeg kerberos ldap libg++
libwww mad maildir md5sum memlimit milter mmx mysql nagios-dns nagios-ntp
nagios-ping nagios-ssh ncurses nls oav pam parse-clocks pcap perl php png python
readline samba sasl skey slang snmp socks5 spell sse ssl tcpd tcsim
transparent-proxy usb virus-scan x86 xml2 zlib"
Comment 1 SpanKY gentoo-dev 2005-04-30 21:35:37 UTC
acl-2.2.27 still misbehave ?
Comment 2 b52 2005-05-01 03:24:56 UTC
No, acl-2.2.27 behaves correctly, sorry forgot it :)
I close this bug.