zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: Permissions directories
Date: Fri, 23 Jun 2000 07:52:10 +0000	[thread overview]
Message-ID: <1000623075210.ZM14185@candle.brasslantern.com> (raw)
In-Reply-To: <200006230709.JAA05621@beta.informatik.hu-berlin.de>

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."

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.

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.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-06-23  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-23  7:09 Sven Wischnowsky
2000-06-23  7:52 ` Bart Schaefer [this message]
2000-06-23  8:04 Sven Wischnowsky

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=1000623075210.ZM14185@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).