zsh-users
 help / color / mirror / code / Atom feed
From: Anthony Heading <aheading@jpmorgan.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@sunsite.dk
Subject: Re: startup delay from compinit
Date: Wed, 8 Oct 2003 11:29:07 +0900	[thread overview]
Message-ID: <20031008022907.GB4263@tkd-fires-02.ja.jpmorgan.com> (raw)
In-Reply-To: <1031007154001.ZM6620@candle.brasslantern.com>

On Tue, Oct 07, 2003 at 03:40:01PM +0000, Bart Schaefer wrote:
> That's rather odd.

Thanks. That was really the hint I needed. Turned out that I
broke everything last time I tried to get it working: I'd
tried to nudge compaudit to accept that files which we have
carefully installed with a special "application" group are
_not_ in fact insecure.  (Looks rather like there is a similar
existing hack for the 'staff' group triggered
by -f /etc/debian_version)

And I was trying to force that externally since I didn't
want to maintain a variant of compaudit in perpetuity,
since compaudit contains the directory scanning code.

But I evidently got it wrong - I'd returned OK from compaudit
without correctly having set _i_files, which meant the
function count was zero, which meant the compdump file
was rejected.

Thanks for the help - I'll have to mull how best to fix
this - turning off security measures (i.e. using -u here)
isn't normally appealing on principle, but when the checking
rules admit to being so arbitrary and system-conditional
they're clearly not always going to work.

Thanks

Anthony

PS. Small patch for conceptual anachronism.  (Young people
today blaa blaa, think they invented everything...)  It's
actually misleading, because it doesn't appear to apply
only to RedHat, yet there is code which is Debian specific
in the file.


--- Completion/compaudit.Orig   Wed Oct  8 11:12:15 2003
+++ Completion/compaudit        Wed Oct  8 11:14:07 2003
@@ -76,7 +76,7 @@
 
 [[ $_i_fail == use ]] && return 0
 
-# RedHat Linux "per-user groups" check.  This is tricky, because it's very
+# "Per-user groups" check.  This is tricky, because it's very
 # difficult to tell whether the sysadmin has put someone else into your
 # "private" group (e.g., via the default group field in /etc/passwd, or
 # by NFS group sharing with an untrustworthy machine).  So we must assume

This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.


  reply	other threads:[~2003-10-08  2:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 10:58 Anthony Heading
2003-10-07 15:09 ` Dan Nelson
2003-10-07 15:40 ` Bart Schaefer
2003-10-08  2:29   ` Anthony Heading [this message]
2003-10-08  4:43     ` 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=20031008022907.GB4263@tkd-fires-02.ja.jpmorgan.com \
    --to=aheading@jpmorgan.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.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).