search

ietf-wg-privacypass / draft-ietf-privacypass-consistency-mirror

K-Check protocol specification
Other
0 stars 5 forks source link

Enforce a minimum validity time? #1

Closed tfpauly closed 1 year ago

tfpauly commented 1 year ago

If the resource can get refreshed very frequently (like every second), a client could still be targeted without detecting an attack. One solution is to have a minimum time for validity.

tfpauly commented 1 year ago

You could also have the mirror police the keys being distributed to make sure that key rotations seem reasonable, and there's not a flipping between keys that could look like targeting.

tfpauly commented 1 year ago

Or ensure that enough clients saw this key before the key changed...

chris-wood commented 1 year ago

From @dvorak42.

chris-wood commented 1 year ago

2 includes a minimum validity time as a mirror configuration parameter.

chris-wood commented 1 year ago

Closing as resolved by #2.

bemasc commented 1 year ago

I think this needs some more motivation. If clients only initiate sessions using currently-fresh resources, then short validity windows do not provide any ability to target individual clients (ignoring clock skew).

I would like to see some more specific rationale for this recommendation, if it is necessary at all.