From: Johannes Berg <johannes@sipsolutions.net>
To: git@vger.kernel.org
Subject: Re: gitweb search page link slightly wrong
Date: Tue, 01 May 2007 12:22:50 +0200 [thread overview]
Message-ID: <1178014970.3483.15.camel@johannes.berg> (raw)
In-Reply-To: <1178014409.3483.12.camel@johannes.berg>
On Tue, 2007-05-01 at 12:13 +0200, Johannes Berg wrote:
> This seems to fix it but I have no idea what it breaks. Command
> injection should be stopped a few lines above that, and no other
> parameter is ever quoted using quotemeta, so I'm not sure what the point
> is, but I suppose it is actually necessary because the search text is
> then wrapped into a regular expression or something?
Ah, I understand now. Here's a possibly complete fix.
From: Johannes Berg <johannes@sipsolutions.net>
Subject: quote $searchtext only before use
$searchtext is used in two ways
(1) to do the search
(2) to put it back into the output
For (1) it needs to have meta chars quoted, but for (2) not, so quote
them only when needed.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
--- git.orig/gitweb/gitweb.perl 2007-05-01 11:58:27.000000000 +0200
+++ git/gitweb/gitweb.perl 2007-05-01 12:20:27.000000000 +0200
@@ -368,7 +368,6 @@ if (defined $searchtext) {
if (length($searchtext) < 2) {
die_error(undef, "At least two characters are required for search parameter");
}
- $searchtext = quotemeta $searchtext;
}
our $searchtype = $cgi->param('st');
@@ -2927,6 +2926,7 @@ sub git_heads_body {
sub git_search_grep_body {
my ($commitlist, $from, $to, $extra) = @_;
+ my $_searchtext = quotemeta $searchtext;
$from = 0 unless defined $from;
$to = $#{$commitlist} if (!defined $to || $#{$commitlist} < $to);
@@ -2951,7 +2951,7 @@ sub git_search_grep_body {
esc_html(chop_str($co{'title'}, 50)) . "<br/>");
my $comment = $co{'comment'};
foreach my $line (@$comment) {
- if ($line =~ m/^(.*)($searchtext)(.*)$/i) {
+ if ($line =~ m/^(.*)($_searchtext)(.*)$/i) {
my $lead = esc_html($1) || "";
$lead = chop_str($lead, 30, 10);
my $match = esc_html($2) || "";
@@ -4325,7 +4325,7 @@ sub git_search {
} elsif ($searchtype eq 'committer') {
$greptype = "--committer=";
}
- $greptype .= $searchtext;
+ $greptype .= quotemeta $searchtext;
my @commitlist = parse_commits($hash, 101, (100 * $page), $greptype);
my $paging_nav = '';
@@ -4374,8 +4374,9 @@ sub git_search {
my $alternate = 1;
$/ = "\n";
my $git_command = git_cmd_str();
+ my $_searchtext = quotemeta $searchtext;
open my $fd, "-|", "$git_command rev-list $hash | " .
- "$git_command diff-tree -r --stdin -S\'$searchtext\'";
+ "$git_command diff-tree -r --stdin -S\'$_searchtext\'";
undef %co;
my @files;
while (my $line = <$fd>) {
prev parent reply other threads:[~2007-05-01 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 20:43 gitweb search page link slightly wrong Johannes Berg
2007-05-01 10:13 ` Johannes Berg
2007-05-01 10:22 ` Johannes Berg [this message]
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=1178014970.3483.15.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=git@vger.kernel.org \
/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