From: Michael Wagner <mail@mwagner.org>
To: "Jakub Narębski" <jnareb@gmail.com>
Subject: Re: [PATCH] gitweb: Harden UTF-8 handling in generated links
Date: Wed, 4 Jun 2014 17:41:29 +0200 [thread overview]
Message-ID: <20140604154128.GA28549@localhost.localdomain> (raw)
In-Reply-To: <53849FB2.7000701@gmail.com>
On Tue, May 27, 2014 at 04:22:42PM +0200, Jakub Narębski wrote:
> W dniu 2014-05-15 21:28, Jakub Narębski pisze:
> > On Thu, May 15, 2014 at 8:48 PM, Michael Wagner <accounts@mwagner.org> wrote:
> >> On Thu, May 15, 2014 at 10:04:24AM +0100, Peter Krefting wrote:
> >>> Michael Wagner:
>
> >> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> >> index a9f57d6..f1414e1 100755
> >> --- a/gitweb/gitweb.perl
> >> +++ b/gitweb/gitweb.perl
> >> @@ -7138,7 +7138,7 @@ sub git_tree {
> >> my @entries = ();
> >> {
> >> local $/ = "\0";
> >> - open my $fd, "-|", git_cmd(), "ls-tree", '-z',
> >> + open my $fd, "-|encoding(UTF-8)", git_cmd(), "ls-tree", '-z',
> >> ($show_sizes ? '-l' : ()), @extra_options, $hash
> >> or die_error(500, "Open git-ls-tree failed");
> >
> > Or put
> >
> > binmode $fd, ':utf8';
> >
> > like in the rest of the code.
> >
> >> @entries = map { chomp; $_ } <$fd>;
> >>
> >
> > Even better solution would be to use
> >
> > use open IN => ':encoding(utf-8)';
> >
> > at the beginning of gitweb.perl, once and for all.
>
> Or harden esc_param / esc_path_info the same way esc_html
> is hardened against missing ':utf8' flag.
>
> -- >8 --
> Subject: [PATCH] gitweb: Harden UTF-8 handling in generated links
>
> esc_html() ensures that its input is properly UTF-8 encoded and marked
> as UTF-8 with to_utf8(). Make esc_param() (used for query parameters
> in generated URLs), esc_path_info() (for escaping path_info
> components) and esc_url() use it too.
>
> This hardens gitweb against errors in UTF-8 handling; because
> to_utf8() is idempotent it won't change correct output.
>
> Reported-by: Michael Wagner <accounts@mwagner.org>
> Signed-off-by: Jakub Narębski <jnareb@gmail.com>
> ---
> gitweb/gitweb.perl | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index a9f57d6..77e1312 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -1548,8 +1548,11 @@ sub to_utf8 {
> sub esc_param {
> my $str = shift;
> return undef unless defined $str;
> +
> + $str = to_utf8($str);
> $str =~ s/([^A-Za-z0-9\-_.~()\/:@ ]+)/CGI::escape($1)/eg;
> $str =~ s/ /\+/g;
> +
> return $str;
> }
>
> @@ -1558,6 +1561,7 @@ sub esc_path_info {
> my $str = shift;
> return undef unless defined $str;
>
> + $str = to_utf8($str);
> # path_info doesn't treat '+' as space (specially), but '?' must be escaped
> $str =~ s/([^A-Za-z0-9\-_.~();\/;:@&= +]+)/CGI::escape($1)/eg;
>
> @@ -1568,8 +1572,11 @@ sub esc_path_info {
> sub esc_url {
> my $str = shift;
> return undef unless defined $str;
> +
> + $str = to_utf8($str);
> $str =~ s/([^A-Za-z0-9\-_.~();\/;?:@&= ]+)/CGI::escape($1)/eg;
> $str =~ s/ /\+/g;
> +
> return $str;
> }
>
> --
> 1.7.1
>
>
While trying to view a "blob_plain" of "Gütekritierien.txt", a 404 error
occured. "git_get_hash_by_path" tries to resolve the hash with the wrong
filename (git ls-tree -z HEAD -- Gütekriterien.txt) and fails.
The filename needs the correct encoding. Something like this is probably
needed for all filenames and should be done at a prior stage:
---
gitweb/gitweb.perl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 77e1312..e4a50e7 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -4725,7 +4725,7 @@ sub git_print_tree_entry {
}
print " | " .
$cgi->a({-href => href(action=>"blob_plain", hash_base=>$hash_base,
- file_name=>"$basedir$t->{'name'}")},
+ file_name=>"$basedir" . to_utf8($t->{'name'}))},
"raw");
print "</td>\n";
--
1.7.1
next prev parent reply other threads:[~2014-06-04 16:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 18:41 [PATCH/RFC] Gitweb: Convert UTF-8 encoded file names Michael Wagner
2014-05-14 21:57 ` Junio C Hamano
2014-05-14 22:25 ` Jakub Narębski
2014-05-15 5:08 ` Michael Wagner
2014-05-15 9:04 ` Peter Krefting
2014-05-15 17:24 ` Junio C Hamano
2014-05-15 18:48 ` Michael Wagner
2014-05-15 19:28 ` Jakub Narębski
2014-05-15 19:37 ` Jakub Narębski
2014-05-15 19:38 ` Junio C Hamano
2014-05-15 20:45 ` Jakub Narębski
2014-05-16 1:26 ` Junio C Hamano
2014-05-16 7:54 ` Jakub Narębski
2014-05-16 17:05 ` Junio C Hamano
2014-05-27 14:18 ` Jakub Narębski
2014-05-16 18:17 ` Junio C Hamano
2014-05-27 14:22 ` [PATCH] gitweb: Harden UTF-8 handling in generated links Jakub Narębski
2014-06-04 15:41 ` Michael Wagner [this message]
2014-06-04 18:47 ` Jakub Narębski
2014-06-04 20:47 ` Michael Wagner
2015-03-23 21:35 ` What's cooking in git.git (Mar 2015, #08; Mon, 23) Junio C Hamano
2014-12-17 14:18 ` [PATCH v4] remote: add --fetch and --both options to set-url Peter Wu
2014-12-17 14:32 ` Jeff King
2014-12-17 14:42 ` Peter Wu
2014-12-17 22:31 ` Junio C Hamano
2015-03-24 22:21 ` What's cooking in git.git (Mar 2015, #08; Mon, 23) Junio C Hamano
2015-03-26 16:18 ` Jeff King
2015-03-24 20:02 ` Junio C Hamano
2015-03-24 20:04 ` Jeff King
2015-03-24 20:08 ` Junio C Hamano
2015-03-24 23:37 ` Junio C Hamano
2015-03-24 22:26 ` Junio C Hamano
2015-03-25 0:37 ` Jakub Narębski
2015-03-25 1:05 ` Junio C Hamano
2014-05-15 12:32 ` [PATCH/RFC] Gitweb: Convert UTF-8 encoded file names Jakub Narębski
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=20140604154128.GA28549@localhost.localdomain \
--to=mail@mwagner.org \
--cc=jnareb@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).