From: Jason Riedy <ejr@EECS.Berkeley.EDU>
To: "Stefan Pfetzing" <stefan.pfetzing@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Git 1.3.2 on Solaris
Date: Mon, 22 May 2006 21:51:15 -0700 [thread overview]
Message-ID: <8157.1148359875@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: <f3d7535d0605222020j2d581bd9j602752659a4b3ac2@mail.gmail.com>
And "Stefan Pfetzing" writes:
- printf ("access: %d\n", access("/etc/motd", X_OK));
[...]
- will return 0 on solaris - when run as root, even though /etc/motd
- is not executeable.
This is explicitly allowed by the SUS, even for non-root:
http://www.opengroup.org/onlinepubs/000095399/functions/access.html
For non-root, some ACL systems could allow you to execute
the file even if there are no execute bits. What a joy
ACLs are. Or NFS uid mappings could play tricks on you,
or... And as you've noticed, this kills [ -x ]. (Failing
to run the hooks in receive-pack.c is noisy but not fatal.
It's the shell scripts that stop.)
I think you're stuck. To disable the hooks for all possible
users, OSes, file systems, etc., you need to remove them.
Or just don't run as root, and hope that the OS isn't
completely insane.
BTW, ERR_RUN_COMMAND_EXEC is never returned. Any failure
to exec will produce an exit code of 128 from die. This
will be an issue when commit becomes a built-in, right?
Jason
next prev parent reply other threads:[~2006-05-23 4:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 23:52 Git 1.3.2 on Solaris Stefan Pfetzing
2006-05-17 1:25 ` Jason Riedy
2006-05-17 2:20 ` Linus Torvalds
2006-05-17 3:26 ` Jason Riedy
2006-05-17 3:49 ` Linus Torvalds
2006-05-17 8:05 ` Stefan Pfetzing
2006-05-17 14:33 ` Linus Torvalds
2006-05-17 15:08 ` Stefan Pfetzing
2006-05-17 16:24 ` Linus Torvalds
2006-05-17 16:35 ` Jason Riedy
2006-05-23 3:20 ` Stefan Pfetzing
2006-05-23 4:51 ` Jason Riedy [this message]
2006-05-23 12:04 ` Stefan Pfetzing
2006-05-23 14:53 ` Linus Torvalds
2006-05-23 15:20 ` Edgar Toernig
2006-05-23 15:31 ` Linus Torvalds
2006-05-23 18:43 ` Edgar Toernig
2006-05-23 18:03 ` Jason Riedy
2006-05-23 18:24 ` Linus Torvalds
2006-05-23 18:48 ` Linus Torvalds
2006-05-26 3:30 ` Stefan Pfetzing
2006-05-17 5:15 ` Ryan Anderson
2006-05-17 8:22 ` Junio C Hamano
2006-05-17 9:03 ` Junio C Hamano
2006-05-17 9:54 ` [PATCH] builtin-grep: workaround for non GNU grep Junio C Hamano
2006-05-17 14:24 ` Linus Torvalds
2006-05-17 17:41 ` Junio C Hamano
2006-05-17 15:39 ` Bertrand Jacquin
2006-05-17 17:42 ` Junio C Hamano
2006-05-17 18:12 ` Linus Torvalds
2006-05-17 18:59 ` Junio C Hamano
2006-05-17 19:42 ` Linus Torvalds
2006-05-17 8:28 ` Git 1.3.2 on Solaris Junio C Hamano
2006-05-17 9:06 ` Stefan Pfetzing
2006-05-17 9:22 ` Junio C Hamano
2006-05-17 10:41 ` Stefan Pfetzing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8157.1148359875@lotus.CS.Berkeley.EDU \
--to=ejr@eecs.berkeley.edu \
--cc=git@vger.kernel.org \
--cc=stefan.pfetzing@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).