Confirmed users
471
edits
Identity/AttachedServices/KeyServerProtocol: Difference between revisions
Jump to navigation
Jump to search
Identity/AttachedServices/KeyServerProtocol (view source)
Revision as of 00:56, 9 July 2013
, 9 July 2013include new SRP salt when resetting the account
m (→Crypto Notes) |
(include new SRP salt when resetting the account) |
||
| Line 381: | Line 381: | ||
= Resetting the Account = | = Resetting the Account = | ||
resetAccount() needs request confidentiality, since the arguments include the newly wrapped kB value and the new SRP verifier, both of which enable a brute-force attack against the password. HAWK provides request integrity. The response is a single "ok" or "fail", conveyed by the HTTP headers, so we do not require response confidentiality, and can live without response integrity. | resetAccount() needs request confidentiality, since the arguments include the newly wrapped kB value and the new SRP verifier, both of which enable a brute-force attack against the password. HAWK provides request integrity. The response is a single "ok" or "fail", conveyed by the HTTP headers, so we do not require response confidentiality, and can live without response integrity. | ||
| Line 393: | Line 391: | ||
The request data will contain kA, wrap(kB), and the SRP verifier, concatenated together. The first | The request data will contain kA, wrap(kB), a new (randomly-generated) SRP salt, and the new SRP verifier, all concatenated together. The first three pieces are fixed-length. We generate enough reqXORkey bytes to cover all four values. | ||
[[File:PICL-IdPAuth-resetAccount.png|Deriving the resetAccount Keys]] | [[File:PICL-IdPAuth-resetAccount.png|Deriving the resetAccount Keys]] | ||