Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zsh compinit: insecure files, run compaudit for list.? #671

Closed
frzyq opened this issue Dec 9, 2019 · 1 comment
Closed

zsh compinit: insecure files, run compaudit for list.? #671

frzyq opened this issue Dec 9, 2019 · 1 comment

Comments

@frzyq
Copy link

frzyq commented Dec 9, 2019

zsh compinit: insecure files, run compaudit for list.
Ignore insecure files and continue [y] or abort compinit [n]? y%

Execute the compaudit command to get the following file path:

here are insecure files:
/usr/local/share/zsh/site-functions/_brew_services
/usr/local/share/zsh/site-functions/_carthage

How can I solve it? thank!

@MaximDevoir
Copy link
Contributor

MaximDevoir commented Feb 19, 2020

From #680

For security reasons compinit also checks if the completion system would use files not owned by root or by the current user, or files in directories that are world- or group-writable or that are not owned by root or by the current user. If such files or directories are found, compinit will ask if the completion system should really be used. To avoid these tests and make all files found be used without asking, use the option -u, and to make compinit silently ignore all insecure files and directories use the option -i. This security check is skipped entirely when the -C option is given.

zsh thinks potentially dangerous files could be loaded and is, therefore, taking steps to try and prevent that.

This question may be a duplicate of #433, #680, and ohmyzsh/ohmyzsh#6835 - check these out for a possible solution. Generally, fixing the issue means changing the permissions or group settings for insecure files, or by setting ZSH_DISABLE_COMPFIX to "true" in your .zshrc file.

Closing this issue in favor of #433. Feel free to reopen if none of the above works for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants