generated from erix/meta
Define restricted metadata ownership policy #38
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-posixabi!38
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/restricted-permission-metadata"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Define compatibility 1.19 mode/ownership changes and individual access queries.
Derive restricted metadata targets from complete authenticated descriptions;
UID zero adds no privilege and ownership cannot transfer to another user.
Preserve explicit unchanged fields, complete ACLs and original group membership.
Depends on #37. Tracks erix/integration#65 and the pure ABI scope in #1.
Original-object authentication, fresh conditional provider effects and native
runtime enforcement remain consumer duties described in erix/posixd#29.
WIP: Define restricted metadata ownership policyto Define restricted metadata ownership policyThe restricted metadata policy and codecs are complete and ready for review. Exact minor-nineteen controls use the public conditional-permission supplier and its explicit device-kind descriptions. Authenticated original-object mediation and actual native effects remain consumer responsibilities.