Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: Re: Permissions directories
- X-seq: zsh-workers 12042
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH: Re: Permissions directories
- Date: Fri, 23 Jun 2000 07:52:10 +0000
- In-reply-to: <200006230709.JAA05621@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <200006230709.JAA05621@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author