Open peeweep opened 1 year ago
The reason to use setfacl
is to facilitate debugging from the outside of the chroot env (for non-root user).
The default ACL should effect only when the file is creating, so the chmod
can successfully change the permission usually.
I don't know why chmod -w,+x
cannot:
https://github.com/adrian-thurston/colm/blob/d00ef7930a9d42469c19a5880744a086065ee20c/src/Makefile.am#L210
I have tried chmod a-w,a+x
and chmod 555
, they all successful.
short log:
full log: https://fars.ee/a6JP
Looks like the
/bin/chmod: colm-wrap: new permissions are r-xrwxrwx, not r-xr-xr-x
cause error.Could it be due to the
setfacl rwx
in chroot.sh? I tried useto remove it, compile passed.