Activation identity omits derived-name grants and disagrees on narrowed bridge grants #414

Closed
opened 2026-10-23 02:07:19 +02:00 by buildagent · 0 comments
Member

Found while reviewing #410 and #412 on 0.41.10.

Reproduced with a focused regression calling activation::inputs_from_record on the same package/host/config before and after changing only PackageActivation.derived_names: false and true produce the identical activation digest. The regression fails before the fix. This grant decides whether whole-file extracted facts may be admitted; dirty_domain already treats it as a bounded reparse, but ActivationPackage/activation_digest omit it.

The same projection has a second inconsistency visible in source: activation::inputs hashes InstalledPackage.bridges (all declarations), whereas inputs_from_record hashes PackageActivation.bridges (the operator-granted subset). A narrowed bridge grant can therefore produce two identities for one activation, or leave the live identity unchanged when the grant changes. Package_digest already covers all declared bridges; the project-specific identity needs the effective granted bridges.

Fix both canonical projections together, preserve capability and bridge canonicalization, and test unchanged-container grant changes. No database schema/ABI/package-byte change is required. Include this in the single conservative identity transition for #412; do not attempt old-activation bounded recovery from incomplete identity evidence.

Found while reviewing #410 and #412 on 0.41.10. Reproduced with a focused regression calling activation::inputs_from_record on the same package/host/config before and after changing only PackageActivation.derived_names: false and true produce the identical activation digest. The regression fails before the fix. This grant decides whether whole-file extracted facts may be admitted; dirty_domain already treats it as a bounded reparse, but ActivationPackage/activation_digest omit it. The same projection has a second inconsistency visible in source: activation::inputs hashes InstalledPackage.bridges (all declarations), whereas inputs_from_record hashes PackageActivation.bridges (the operator-granted subset). A narrowed bridge grant can therefore produce two identities for one activation, or leave the live identity unchanged when the grant changes. Package_digest already covers all declared bridges; the project-specific identity needs the effective granted bridges. Fix both canonical projections together, preserve capability and bridge canonicalization, and test unchanged-container grant changes. No database schema/ABI/package-byte change is required. Include this in the single conservative identity transition for #412; do not attempt old-activation bounded recovery from incomplete identity evidence.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
h-dv/code-index#414
No description provided.