Probe: lifecycle timing bounds 600s/300s (audit G12) #56
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Ting/Vedanta#56
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?
The ratified contract requires renewal no later than 10 minutes before expiry and predecessor overlap no greater than 5 minutes, but the plugin stores displaced predecessors valid until explicit invalidation with no renewBefore, scheduler, or capture-double proving the bounds.
Probe paths: openbao-plugin/src/lease.rs, openbao-plugin/src/backend.rs, and openbao-plugin/src/issue.rs.
Result schema: renewal timestamp; predecessor acceptance or rejection; exact invalidation time compared with the 600s and 300s bounds.
Evidence: audit 2026-09-19/20 G12 and S7-F4.