missing parameter in algorithm specification

huebner_p's Avatar

huebner_p

27 Jan, 2019 12:30 PM

Hi,
i missed the explanation of the key context parameter in the "masterpassword-algorithm.pdf".
After digging into the code, i assume, that the seed for the site key is
scope.LEN(<site name>).<site name>.counter.<LEN(<key context>).<key context>

instead
scope.LEN(<site name>).<site name>.counter

as described under "Phase2: Your site key"
Is this correct?
best Regards
Peter

  1. 1 Posted by huebner_p on 28 Jan, 2019 03:24 PM

    huebner_p's Avatar

    Hi,
    i would like to ask again to get informations about handling of key_context parameter.
    Is it as i guess or is that parameter specified different?

    best Regards
    Peter

  2. Support Staff 2 Posted by Maarten Billemo... on 28 Jan, 2019 05:58 PM

    Maarten Billemont's Avatar

    Yes, that's correct. The PDF is missing the keyContext parameter, but that's mainly because the PDF deals with the "authentication" scenario only, and the context is not used in this situation.

    The key context is used in the recovery situation (where it forms the "keyword" from the security question you're answering). It is also used in the situation where mpw generates cryptographic keys. The PDF can be amended to include these situations, but currently focuses on the authentication scenario only.

  3. 3 Posted by huebner_p on 29 Jan, 2019 05:47 AM

    huebner_p's Avatar

    Hi Marten,
    thanks a lot for the explanation.

    best Regards
    Peter

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

10 Feb, 2019 07:07 PM
10 Feb, 2019 12:06 AM
04 Feb, 2019 06:18 PM
04 Feb, 2019 06:08 PM
02 Feb, 2019 09:34 AM