-
Notifications
You must be signed in to change notification settings - Fork 210
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
mise trust follows symbolic links making it difficult to manage #1501
Labels
bug
Something isn't working
Comments
AntonFriberg
added a commit
to AntonFriberg/dotfiles
that referenced
this issue
Jan 22, 2024
Note that trusted_config_paths does not work due to issues with mise and symbolic links. https: //github.com/jdx/mise/issues/1501 Change-Id: I36b5d5848b703b620a3f98dfd18dc0a0f52764b2
With symlinks, wouldn't the paranoid thing be to hash both:
Then, when changes are made to the underlying file, only one file would need to be re-hashed. Perhaps |
jdx
added a commit
that referenced
this issue
Jan 24, 2024
jdx
added a commit
that referenced
this issue
Jan 24, 2024
jdx
added a commit
that referenced
this issue
Jan 24, 2024
* config: do not follow symbolic links for trusted paths Fixes #1501 * Commit from GitHub Actions (test) --------- Co-authored-by: mise[bot] <123107610+mise-en-dev@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
It is common to manage dotfiles using symbolic links to version controlled repos or by utilizing more advanced tools such as Nix with Home-Manager. In both of these cases the
~.config/mise
files will be populated by symbolic links to configuration that is stored elsewhere instead of actual files.To Reproduce
Expected behavior
I would expect that I should trust the symbolic link instead of needing to trust the source of the link.
mise doctor
outputAdditional context
In my case it is very difficult to trust the source of the symbolic link since it is a generate path from Nix that changes each time the configuration of mise changes.
So instead of simply trusting
~/.config/mise/config.toml
I need to trust/nix/store/3d7m3pfiv48hl1lp70b3pnyhziwbyvrh-mise-config
You can probably see the issue by just seeing the output of manual trust of the file. I would really like to have global config with trusted directories instead of having to manually run
mise trust
every time I change the source of the Nix configuration.The text was updated successfully, but these errors were encountered: