git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] use filetest pragma to work with ACL

From
GCGuillaume Castagnino <casta@xwing.info>
Date
Oct 19, 2017, 07:53 UTC
Message-ID
<1508399608.4529.10.camel@xwing.info>
In-Reply-To
<20171018212451.goqxu4qq6aqe4tpl@sigill.intra.peff.net>
Hi,
Le mercredi 18 octobre 2017 à 17:24 -0400, Jeff King a écrit :
Show 25 quoted lines
> On Wed, Oct 18, 2017 at 07:55:31PM +0000, Guillaume Castagnino wrote:
> 
> > From: Guillaume Castagnino <casta@xwing.info>
> > [...]
> 
> Stefan raised a few meta issues, all of which I agree with. But I had
> some questions about the patch itself:
> 
> > diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> > index 9208f42ed1753..0ee7f304ce2b1 100755
> > --- a/gitweb/gitweb.perl
> > +++ b/gitweb/gitweb.perl
> > @@ -3072,6 +3072,7 @@ sub git_get_projects_list {
> >  				# only directories can be git
> > repositories
> >  				return unless (-d $_);
> >  				# need search permission
> > +				use filetest 'access';
> >  				return unless (-x $_);
> 
> This "use" will unconditionally at compile-time (such as "compile" is
> for perl, anyway). Which raises a few questions:
> 
>   - would we want to use "require" instead to avoid loading when we
>     don't enter this function?

I was under the impression that as this is a pragma affecting perl “compiler”, you have to always use “use”, not require, as the pragma initialisation has to be done before code is run.

Show 8 quoted lines
>   - If the answer to the above is "no" (e.g., because we basically
>     always need it; I didn't check), should it go at the top of the
>     script with the other "use" directives?
> 
>     I think this is a scoped pragma, so what you have here affects
> only
>     this particular "-x". But wouldn't other uses of "-x" potentially
>     want the same benefit?

I quickly grepped the code, I did not see other calls that could benefits from the pragma, but it could be indeed nice to move it at the top to avoid future issues with such tests and POSIX ACL.

Show 8 quoted lines
>   - Do all relevant versions of perl ship with filetest? According to
>     Module::Corelist, it first shipped with perl 5.6. In general I
> think
>     we treat that as a minimum for our perl scripts, though I do
> notice
>     that the gitweb script says "use 5.008". I'm not sure how
> realistic
>     that is.
So the CGI already requires perl 5.8, so it’s fine I think.
Attached a cleanup proposal and moving the use at the top.

Thanks Guillaume

-- 
Guillaume Castagnino
    casta@xwing.info / guillaume@castagnino.org

From 4d5a082970063b34d3dbdf5b9a577624310057d6 Mon Sep 17 00:00:00 2001
From: Guillaume Castagnino <casta@xwing.info>
Date: Thu, 19 Oct 2017 09:32:46 +0200
Subject: [PATCH] gitweb: use filetest to allow ACLs

In commit 46a1385 (gitweb: skip unreadable subdirectories, 2017-07-18)
we forgot to handle non-unix ACLs as well. Fix this.

Signed-off-by: Guillaume Castagnino <casta@xwing.info>
---
 gitweb/gitweb.perl | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 9208f42ed..6ac49eaf3 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -10,6 +10,8 @@
 use 5.008;
 use strict;
 use warnings;
+# handle ACL in file access tests
+use filetest 'access';
 use CGI qw(:standard :escapeHTML -nosticky);
 use CGI::Util qw(unescape);
 use CGI::Carp qw(fatalsToBrowser set_message);
-- 
2.14.2
Previous: Jeff KingNext: Jeff King
Message 4 of 6 in “use filetest pragma to work with ACL”
  1. use filetest pragma to work with ACLGuillaume Castagnino, Oct 18, 2017
  2. Stefan BellerOct 18, 2017
  3. Jeff KingOct 18, 2017
  4. Guillaume CastagninoOct 19, 2017
  5. Jeff KingOct 19, 2017
  6. Junio C HamanoOct 24, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.