WICG/webpackage

Deal with clock skew

Open

#141 opened on Mar 7, 2018

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Go (124 forks)github user discovery
help wanted

Repository metrics

Stars
 (1,257 stars)
PR merge metrics
 (Avg merge 19h 38m) (1 merged PR in 30d)

Description

Our strictness in enforcing being within the 7-day signature validity period interacts badly with skewed clocks. Do we want to encourage signers to pre-date the signature's timestamp by X hours, or require clients to trust signatures that start being valid in X hours, or something else?

Contributor guide

Research direction
Research and evaluate approaches to handle clock skew in signature validity: pre dating signatures by X hours, trusting future start times by X hours, or other mechanisms. Consider trade offs and draft recommendations.
Tech stack
go
Domain
security
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
understanding of web packaging signaturesclock skew concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30