[FEATURE] Audit authority, code quality and documentation in lib-crc #1
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-crc#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem and motivation
Review the CRC library and its storage callers while preserving their checksum
dialects. A matching checksum must never authorize access or authenticate data.
Proposed behavior and scope
Keep reflected IEEE CRC-32, non-reflected IEEE CRC-32 and Castagnoli CRC-32C
compatible. Cover the complete crate, workflow, documentation and the
lib-partitionande2fsdconsumer selections.Authority, security and reliability
Calls borrow immutable bytes and scalar seeds, return scalar state, and retain
nothing. The crate has no allocation, I/O, capabilities, unsafe code or FFI.
Replay, revocation and cleanup protocols do not apply to this synchronous
computation. Consumers own format validation, authentication and scheduling.
Acceptance criteria
Alternatives and tradeoffs
The shared reflected recurrence avoids duplication. Bitwise updates use constant
space and eight state steps per byte. No measured consumer bottleneck justifies
tables or hardware acceleration; preserve the auditable implementation.
Tracking and rollout
PR 2 contains the signed
changes. Phase completion
tracks the separate guest and toolchain builds. Cargo manifests track
main;CI retains exact original revisions for each complete resolved graph.
[FEATURE] [P02.R36] Audit authority, code quality and documentation in lib-crcto [FEATURE] Audit authority, code quality and documentation in lib-crcThe signed checkpoint completes the full public/private inline review. It corrects the shared accumulator's caller description and includes private items in CI rustdoc. Algorithm, API and existing test behavior are unchanged. Wider audit, consumer and timing work remain open.
Completed the whole crate and workflow review at b18e256b. The API remains pure, allocation-free computation with no retained authority or incidental input limit. The implementation and all eight documented public routes are unchanged from the reviewed source.
Component run 42 passes. Partition run 42 and filesystem run 427 select the same implementation and pass their checksum consumer cases. Closing the component audit; PR 2 remains draft for maintainer review.