Implement mandatory signature checking
Registered by
Jeff Johnson
RPM is fully prepared to verify package signatures.
However, signature/digest checking is routinely disabled by depsolvers
inconsistently: each depsolver has different signature checking policies.
A consistent signature verification policy, set by the end-user, not by each application,
is needed for any rational security audit to be performed.
Blueprint information
- Status:
- Started
- Approver:
- Jeff Johnson
- Priority:
- Essential
- Drafter:
- Jeff Johnson
- Direction:
- Approved
- Assignee:
- Jeff Johnson
- Definition:
- Approved
- Series goal:
- Accepted for 5.3
- Implementation:
-
Good progress
- Milestone target:
-
5.4.11
- Started by
- Jeff Johnson
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
rpm-5.3.2 adds a non-repudiable DSA signature, thereby guaranteeing ALL packages have a signature.
The remaining implementation is to add the logic to fail packages that do not
have a signature.
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
