Skip to content

Clamp hostile expires_in in TemporalBearerGuard - #98

Merged
kilork merged 1 commit into
masterfrom
fix-94-bearer-expires-in
Oct 4, 2026
Merged

kilork merged 1 commit into
masterfrom
fix-94-bearer-expires-in

Conversation

@kilork

@kilork kilork commented Aug 30, 2026

Copy link
Copy Markdown
Owner

Fixes #94

expires_in is provider-controlled and was cast to i64 for the duration:
values above i64::MAX wrap and the DateTime addition can panic. Clamp to
100 years. A missing expires_in still means the guard never expires - now
documented by this change note in #94.

Fixes #94
@kilork
kilork force-pushed the fix-94-bearer-expires-in branch from d25aa4f to d3542fc Compare October 4, 2026 19:36
@kilork kilork self-assigned this Oct 4, 2026
@kilork
kilork merged commit bc13d28 into master Oct 4, 2026
2 checks passed
@kilork
kilork deleted the fix-94-bearer-expires-in branch October 4, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TemporalBearerGuard: hostile expires_in can panic, missing expires_in never expires

1 participant