From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: Permissions directories
Date: Fri, 23 Jun 2000 10:04:49 +0200 (MET DST) [thread overview]
Message-ID: <200006230804.KAA05838@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Fri, 23 Jun 2000 07:52:10 +0000
Bart Schaefer wrote:
> On Jun 23, 9:09am, Sven Wischnowsky wrote:
> } Subject: PATCH: Re: Permissions directories
> }
> } + # We search for:
> } + # - world/group-writable directories in fpath not owned by root or the user
> } + # - parent-directories of directories in fpath that are world/group-writable
> } + # and not owned by root or the user
>
> I think you meant "... OR not owned by ..." rather than "and."
That's a Germanism[1], should have known, that, though.
> Of course it now occurs to me that the one remaining problem is that if
> the directory or file containing the compinit function is writable, none
> of this is going to make any difference.
Indeed >;->
> I suppose at some point you just have to trust your installation. I'd be
> tempted to suggest that compinit should be at least partially moved into
> the C code in the computil module, but then we're not doing any ownership/
> writability tests on dynamically-loaded modules in the C code, either.
I was tempted to do that for the loop(s) that read the #compdef
tags (to make it faster). But even this (and the globbing even more)
is so much more convenient to write in shell code...
Bye
Sven
Index: Completion/Core/compinit
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Core/compinit,v
retrieving revision 1.7
diff -u -r1.7 compinit
--- Completion/Core/compinit 2000/06/23 07:10:41 1.7
+++ Completion/Core/compinit 2000/06/23 08:01:05
@@ -348,13 +348,13 @@
typeset _i_q
# We search for:
- # - world/group-writable directories in fpath not owned by root or the user
+ # - world/group-writable directories in fpath not owned by root and the user
# - parent-directories of directories in fpath that are world/group-writable
- # and not owned by root or the user (that would allow someone to put a
+ # and not owned by root and the user (that would allow someone to put a
# digest file for one of the directories into the parent directory)
- # - digest files for one of the directories in fpath not owned by root or
+ # - digest files for one of the directories in fpath not owned by root and
# the user
- # - and for files in directories from fpath not owned by root or the user
+ # - and for files in directories from fpath not owned by root and the user
# (including zwc files)
_i_wdirs=( ${^fpath}(Nf:g+w:,f:o+w:,^u0u${EUID})
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-23 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-23 8:04 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-23 7:09 Sven Wischnowsky
2000-06-23 7:52 ` Bart Schaefer
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=200006230804.KAA05838@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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).