Skip to content
This repository was archived by the owner on Oct 30, 2024. It is now read-only.

Incorrect scrypt kdf defaults? #55

Closed
wjmelements opened this issue Jul 10, 2018 · 2 comments
Closed

Incorrect scrypt kdf defaults? #55

wjmelements opened this issue Jul 10, 2018 · 2 comments

Comments

@wjmelements
Copy link

wjmelements commented Jul 10, 2018

Should the defaults for scrypt kdf be

p = 1
r = 8

instead of

p = 8
r = 1

Just looking at my own keystore, these defaults looked flipped.

@wjmelements
Copy link
Author

@tinybike do you know who could verify this?

@tinybike
Copy link
Member

@wjmelements Good question... I have keystore files with examples of both. It does look like the current version of geth defaults to p=1, r=8 for geth account new. However, I see examples with p=8, r=1 in the docs, for example https://github.com/ethereum/wiki/wiki/Web3-Secret-Storage-Definition#scrypt. My guess is that p=1, r=8 is preferable (since the point of scrypt is to be memory hard) but I'm not sure.

Since keythereum is supposed to be congruent with geth, it's probably sensible to change this. Might be worth also pinging https://gitter.im/ethereum/go-ethereum to ask about this though.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants