From: Erik Faye-Lund <kusmabite@gmail.com>
To: Theo Niessink <niessink@martinic.com>
Cc: Junio C Hamano <gitster@pobox.com>, Johannes Sixt <j6t@kdbg.org>,
git@vger.kernel.org, johannes.schindelin@gmx.de
Subject: Re: [PATCH 3/3] verify_path: consider dos drive prefix
Date: Wed, 8 Jun 2011 12:45:28 +0200 [thread overview]
Message-ID: <BANLkTinTJh9oOTHi5js7n-sy8+pmMa_vtQ@mail.gmail.com> (raw)
In-Reply-To: <DAFDEB13CE4944C18AAF3F20994AEF2E@martinic.local>
On Wed, Jun 8, 2011 at 11:55 AM, Theo Niessink <niessink@martinic.com> wrote:
> Junio C Hamano wrote:
>> Here is what I queued last night. If it looks Ok then I'll merge it down
>> to 'next'.
>
> I have run a couple of quick tests, and everything seems OK, except the
> following backslashed paths, which are verified OK while they should be
> rejected:
>
> foo\.\bar
> foo\..\bar
>
> This is caused by verify_dotfile(), which doesn't use is_dir_sep(). So I
> propose this patch on verify_dotfile():
>
> diff --git a/read-cache.c b/read-cache.c
> index 282c0c1..72be7cd 100644
> --- a/read-cache.c
> +++ b/read-cache.c
> @@ -726,11 +726,12 @@ static int verify_dotfile(const char *rest)
> * has already been discarded, we now test
> * the rest.
> */
> - switch (*rest) {
> +
> /* "." is not allowed */
> - case '\0': case '/':
> + if (*rest == '\0' || is_dir_sep(*rest))
> return 0;
>
> + switch (*rest) {
> /*
> * ".git" followed by NUL or slash is bad. This
> * shares the path end test with the ".." case.
> @@ -743,7 +744,7 @@ static int verify_dotfile(const char *rest)
> rest += 2;
> /* fallthrough */
> case '.':
> - if (rest[1] == '\0' || rest[1] == '/')
> + if (rest[1] == '\0' || is_dir_sep(rest[1]))
> return 0;
> }
> return 1;
>
>
>
This looks obviously correct to me. Thanks for spotting the problem.
Would you mind writing up a commit-message and supply a sign-off?
next prev parent reply other threads:[~2011-06-08 10:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 9:55 [PATCH 3/3] verify_path: consider dos drive prefix Theo Niessink
2011-06-08 10:45 ` Erik Faye-Lund [this message]
2011-06-08 12:04 ` Theo Niessink
2011-06-08 12:15 ` Erik Faye-Lund
-- strict thread matches above, loose matches on Subject: below --
2011-05-27 16:00 [PATCH maint 0/3] do not write files outside of work-dir Erik Faye-Lund
2011-05-27 16:00 ` [PATCH 3/3] verify_path: consider dos drive prefix Erik Faye-Lund
2011-05-27 18:58 ` Johannes Sixt
2011-05-30 9:32 ` Erik Faye-Lund
2011-05-30 10:58 ` Theo Niessink
2011-05-30 11:17 ` Erik Faye-Lund
2011-06-07 3:46 ` Junio C Hamano
2011-06-07 10:07 ` Erik Faye-Lund
2011-06-07 19:09 ` Erik Faye-Lund
2011-06-07 19:22 ` Junio C Hamano
2011-06-07 19:32 ` Erik Faye-Lund
2011-06-07 11:46 ` Theo Niessink
2011-05-30 20:23 ` Johannes Sixt
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=BANLkTinTJh9oOTHi5js7n-sy8+pmMa_vtQ@mail.gmail.com \
--to=kusmabite@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=johannes.schindelin@gmx.de \
--cc=niessink@martinic.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).