Skip to content

Output hash does not match firebase hash #8

@decaffjoe

Description

@decaffjoe

When using the same parameters (memCost, rounds, saltSeparator, signerKey) this library does not always produce the same hash as the hash stored on firebase.

For instance, with the same init parameters, password and salt this library produces this hash:

ERD5RmAyHp21ebGFfeurPplBd9veb7T9mme+IQ1X68aaOVw5ZFhou84297k/x8zLHFoo+vQXiy2VRxq5pGqc0g==

while the firebase hash is actually:

ERD5RmAyHp21ebGFfeurPplBd9veb7T9mme-IQ1X68aaOVw5ZFhou84297k_x8zLHFoo-vQXiy2VRxq5pGqc0g==

In this case, replacing the + char with - and / with _ makes the library hash equal the firebase hash.

I am wondering if this is due to some type of encoding difference between the library and firebase? In the short term, is anyone aware of other differences like this that should be accounted for?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions