4 Commits (101f017ef544c41c4cb577ea19611888e79b13de)

Author	SHA1	Message	Date
Sloane Hertel	e84240db84	Fix installing roles containing symlinks (#82911) ... * Fix installing roles containing symlinks Fix sanitizing tarfile symlinks relative to the link directory instead of the archive For example: role ├── handlers │ └── utils.yml -> ../tasks/utils/suite.yml The link ../tasks/utils/suite.yml will resolve to a path outside of the link's directory, but within the role role/handlers/../tasks/utils/suite.yml the resolved path relative to the role is tasks/utils/suite.yml, but if the symlink is set to that value, tarfile would extract it from role/handlers/tasks/utils/suite.yml * Replace overly forgiving test case with tests for a symlink in a subdirectory of the archive and a symlink in the archive dir when these are not equivalent. * Build test case from role files to make it easier to add test cases Fixes #82702 Fixes #81965 Fixes #82051	6 months ago
Sloane Hertel	3a42a00368	Targeted fix for installing roles with symlinks containing '..' (#82165) ... Set the tarfile attribute to a normalized value from unfrackpath instead of validating path parts and omiting potentially invald parts Allow tarfile paths/links containing '..', '$', '~' as long as the normalized realpath is in the tarfile's role directory	11 months ago
Matt Clay	9f899f9492	Require `from __future__ import annotations` (#81902)	1 year ago
Matt Martz	ddf0311c63	Prevent roles from using symlinks to overwrite files outside of the installation directory (#81780) ... * Sanitize linkname during role installs * Add tests * add clog frag	1 year ago