Seems like running `unsymlink-lib --migrate` while under 077 umask leaves the system broken for non-root users due to path traversal issues caused by non-world readable directories. Running rollback, changing umask to 022 and re-running --migrate works. Perhaps the tool should set umask 022 for it's own process tree.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fbd444389acc5883d05d6afad19f9ace19a365eb commit fbd444389acc5883d05d6afad19f9ace19a365eb Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2019-06-16 17:34:37 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-06-16 17:35:03 +0000 app-portage/unsymlink-lib: Bump to v16 Bump to version 16. Fixes wrong umask. Bug: https://bugs.gentoo.org/688164 Signed-off-by: Michał Górny <mgorny@gentoo.org> app-portage/unsymlink-lib/Manifest | 1 + app-portage/unsymlink-lib/unsymlink-lib-16.ebuild | 30 +++++++++++++++++++++++ 2 files changed, 31 insertions(+)
Fix released as v16. Since this is a major issue, please test and stabilize.
amd64 stable
