Thank you, this is a great tool. Everything is working perfectly as far as 
I can tell. It also works with fish shell by adding .config/fish to $chdirs.

I was thinking about what kinds of files, not present in the default 
installation but possibly added to a user's system, might need to be added 
to $chdirs and $chfiles manually. Perhaps such a list could go in the 
documentation. Some examples:

1. Any files sourced by your shell startup scripts that are in the 
persistent private volume, e.g., files that provide completion information 
for your shell but that aren't in the template.

2. Executables installed by other package managers that don't use the 
normal paths. For example, go uses $HOME/go/bin by default; cabal uses 
$HOME/.cabal/bin. Probably not worth trying to list all of these, but 
rather just noting the risk. Of courses, users that make regular use of 
these package managers might not want to enable this kind of hardening for 
convenience reasons.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/746d4255-ab3d-4a70-847b-690700bcbff3%40googlegroups.com.

Reply via email to