search

nix-community / home-manager

Manage a user environment using Nix [maintainer=@rycee]
https://nix-community.github.io/home-manager/
MIT License
6.8k stars 1.78k forks source link

Add an option to replace symlinks with bind mounts #5521

Open DADA30000 opened 3 months ago

DADA30000 commented 3 months ago

Description

This might sound dumb, but it would be nice to have an option that makes symlinks created by home-manager owned by root (like hyprland.conf symlink), so they could not be deleted/replaced with other config file for additional security, at least when using home-manager as a NixOS module

DADA30000 commented 3 months ago

Oh and also set 775 permission on them

DADA30000 commented 3 months ago

Oh, after some research I found out that symlinks don't have any permissions, they are attached to directory permissions, maybe replace symlinks with mount --bind?

stale[bot] commented 2 weeks ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.