Closed
Bug 963141
Opened 11 years ago
Closed 11 years ago
Make APK signer nonce checking more robust against replays
Categories
(Marketplace Graveyard :: Integration, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
2014-03-04
People
(Reporter: kumar, Assigned: kumar)
References
Details
(Whiteboard: [A4A][qa-])
While using Hawk for authentication (bug 962831) we need to check nonces in a robust way to prevent replay attacks. We will already have a timestamp expiration; nonce checking is a way to limit replays before the timestamp expires. We need to use something like redis to store the nonce temporarily (until the timestamp expires) to reject duplicate nonces.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → kumar.mcmillan
Updated•11 years ago
|
Priority: P3 → P2
Updated•11 years ago
|
Whiteboard: [A4A]
Assignee | ||
Comment 1•11 years ago
|
||
nonce checking with Django cache is implemented here: https://github.com/mozilla/apk-signer/commit/5acae04643f943b1c6d5f5ea695bd8bf48a20eeb
Right now it uses memory cache but once we have memcache (bug 976729) it should work just the same
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2014-03-04
Comment 2•11 years ago
|
||
Please add some STRs to this bug or mark it as [qa-]
Assignee | ||
Updated•11 years ago
|
Whiteboard: [A4A] → [A4A][qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•