Exsh launch validation shadows the authority helper #196

Open
opened 2026-10-24 16:31:07 +02:00 by erikinkinen · 0 comments
Owner

Summary

Exsh launch validation shadows its imported authority helper with a local list. A valid Exsh record reaching the profile comparison would call that list and fail, blocking object-store installation.

Reproduction

Pass an otherwise canonical Exsh launch record to validate_launch_manifest in scripts/install-dynlink-object-store.py. After the header, digest and row checks, the function reaches the Exsh profile comparison. Its local authority_rows list has the same name as the helper called there.

This is a source-confirmed finding. No runtime reproduction or CI attribution is claimed yet.

Expected and actual behavior

Valid Exsh records should be compared with the selected profile's canonical authority rows. The local list shadows authority_rows(exsh_profile), so reaching that call would raise TypeError instead of completing the comparison. Malformed records must continue to be rejected.

Environment and identity

The finding is in the signed local Integration source on feature/posix-compat, during typed product-install planning. It concerns the host Python validator, before image or guest execution. No earlier working revision has been established.

Evidence and prior checks

Source inspection confirms the list declaration, append and subsequent call in the same function. The product migration is extracting shared admission logic for native population and the retained existing-media installer. That extraction must preserve every profile, digest and authority check while removing the collision.

Tracking

Related to typed ext4 product population and Phase 6 completion.

  • Remove the local/helper name collision in the shared validator.
  • Add meaningful valid-profile and changed-authority controls for both installer consumers.
  • Complete the focused controls with the corrected source.
## Summary Exsh launch validation shadows its imported authority helper with a local list. A valid Exsh record reaching the profile comparison would call that list and fail, blocking object-store installation. ## Reproduction Pass an otherwise canonical Exsh launch record to `validate_launch_manifest` in `scripts/install-dynlink-object-store.py`. After the header, digest and row checks, the function reaches the Exsh profile comparison. Its local `authority_rows` list has the same name as the helper called there. This is a source-confirmed finding. No runtime reproduction or CI attribution is claimed yet. ## Expected and actual behavior Valid Exsh records should be compared with the selected profile's canonical authority rows. The local list shadows `authority_rows(exsh_profile)`, so reaching that call would raise `TypeError` instead of completing the comparison. Malformed records must continue to be rejected. ## Environment and identity The finding is in the signed local Integration source on `feature/posix-compat`, during typed product-install planning. It concerns the host Python validator, before image or guest execution. No earlier working revision has been established. ## Evidence and prior checks Source inspection confirms the list declaration, append and subsequent call in the same function. The product migration is extracting shared admission logic for native population and the retained existing-media installer. That extraction must preserve every profile, digest and authority check while removing the collision. ## Tracking Related to [typed ext4 product population](https://git.erikinkinen.fi/erix/boot-tool/issues/11) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [ ] Remove the local/helper name collision in the shared validator. - [ ] Add meaningful valid-profile and changed-authority controls for both installer consumers. - [ ] Complete the focused controls with the corrected source.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:22 +01:00
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
erix/integration#196
No description provided.