Skip to content

Conversation

@maxmoehl
Copy link
Member

Summary

When extended file attributes are set on a file in the archive, try to preserve them on extraction but do not fail when the user does not have permission to set them or if they are not supported. This should prevent existing usages from breaking while also enabling users to preserve extended file attributes.

Part of cloudfoundry/diego-release#1092

Backward Compatibility

Breaking Change? No

When extended file attributes are set on a file in the archive, try to
preserve them on extraction but do not fail when the user does not have
permission to set them or if they are not supported. This should prevent
existing usages from breaking while also enabling users to preserve
extended file attributes.
@winkingturtle-vmw
Copy link
Contributor

Thanks @maxmoehl for this PR. It looks good to me. Can you comment on whether it's possible to add a test coverage for this or not ?

@maxmoehl
Copy link
Member Author

maxmoehl commented Jan 5, 2026

The main issue is that writing file capabilities requires the SETFCAP capability which is not given to users by default, executing such tests would require elevated privileges.

I don't think we want to require sudo to run the tests 😅

@winkingturtle-vmw winkingturtle-vmw merged commit f297303 into cloudfoundry:main Jan 6, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants