From: Daniel Tameling <tamelingdaniel@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: [Bug] Strange Globing Behaviour when used with sudo
Date: Sat, 2 Jun 2018 20:17:19 +0200 [thread overview]
Message-ID: <20180602181719.vzcnij3fvx7eueuk@Daniels-MacBook-Air.local> (raw)
In-Reply-To: <01B9BB58-DDAE-4056-AD9A-2367DC3AC20D@kba.biglobe.ne.jp>
On Fri, Jun 01, 2018 at 11:08:30PM +0900, Jun T. wrote:
>
> > 2018/06/01 03:15, Daniel Tameling <tamelingdaniel@gmail.com> wrote:
> >
> > As s is NULL and buf is in the example ./file/, statfullpath adds to
> > buf a . so that it's "./file/.".
> (snip)
> > So one possibility to fix this is to
> > call stat before adding the . to ./file/, and the return non-zero if
> > it is not a directory.
>
> Yes, but users can add '.' by themselves, for example
> sudo zsh -c 'echo */.'. And of course you can not just
> "return !S_ISDIR(st->st_mode)", and st may be NULL.
>
> I've also fond that stat("file/..") is similarly broken.
>
> In the patch below, I enclosed everything within "#ifdef __APPLE__"
> to minimize the side effects. It is difficult to detect the bug
> by configure since it requires sudo.
>
Your patch works, but it didn't solve everything. So while
$ sudo zsh -c 'echo */..
results in "no matches found", but already adding a slash and you get
again output:
$ sudo zsh -c 'echo */../
file/../
This is not so easy to fix because you can continue the path after .. :
$ sudo zsh -c 'echo */../.././directory/'
file/../.././directory/
So fixing this would probably mean, you need to iterate over the path,
and whenever encountering "." or ".." checking whether everything
before is really a directory.
But note that fixing the problem would also lead to a behavior that
some might find counter-intuitive:
$ sudo zsh -c 'ls file/..'
file
$ sudo zsh -c 'ls */..'
zsh:1: no matches found: */..
Btw:
I noticed bash manages to trigger the ls error message when zsh
outputs "no matches found"
$ bash -c 'ls */..'
ls: cannot access '*/..': No such file or directory
--
Best,
Daniel
next prev parent reply other threads:[~2018-06-02 18:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 17:11 Bengt Brodersen
2018-05-30 18:06 ` Bart Schaefer
2018-05-30 19:15 ` Daniel Shahaf
2018-05-30 20:23 ` Phil Pennock
2018-05-30 20:44 ` Bengt Brodersen
2018-05-30 20:49 ` Bengt Brodersen
2018-05-31 8:44 ` Peter Stephenson
[not found] ` <20180531094403.05b62bee@camnpupstephen.cam.scsc.local>
2018-05-31 8:49 ` Peter Stephenson
2018-05-31 11:39 ` Jun T
2018-05-31 15:29 ` Peter Stephenson
2018-05-31 18:15 ` Daniel Tameling
2018-06-01 14:08 ` Jun T.
2018-06-02 18:17 ` Daniel Tameling [this message]
2018-06-03 16:30 ` Jun T.
2018-06-03 18:48 ` Daniel Tameling
2018-06-03 19:17 ` dana
2018-06-04 1:23 ` Jun T
2018-06-04 12:48 ` Jun T
2018-06-14 12:26 ` Bengt Brodersen
2018-05-31 6:37 ` Martijn Dekker
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=20180602181719.vzcnij3fvx7eueuk@Daniels-MacBook-Air.local \
--to=tamelingdaniel@gmail.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).