Closed
Bug 650435
Opened 14 years ago
Closed 14 years ago
Reduce timestamp granularity
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 546715
People
(Reporter: rnewman, Unassigned)
Details
I recall discussions that we'd like to drop the granularity of timestamps from 1/100sec to 1sec. I believe the motivation for this is to reduce the possibility of a timing attack. I couldn't find an existing bug, so here goes.
This should have minimal effect on the client, so long as timestamps match up everywhere. A gradual deployment -- that is, truncating/rounding only new timestamps, not old ones -- would be least troublesome.
More details from those who know, plz!
Comment 1•14 years ago
|
||
The reason isn't so much timing attacks but reducing the size of the timestamp column in MySQL.
Reporter | ||
Comment 2•14 years ago
|
||
#services.log:14:22 <@mconnor> there's also a "resist timing attacks" rfe to reduce timestamps to be 10ths of a second, or whole seconds
Comment 3•14 years ago
|
||
It's both, though the desire to reduce db footprint predates the (admittedly small) security concern.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•