-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement tranformation from mnemonic phrase to seed #12
Comments
We need to test program behaviour when mnemonic isn't valid UTF-8. #21 (comment) |
Please add validation of user's password.
PA193_mnemonic_Slytherin/PA193_mnemonic_Slytherin/mnemonic.py Lines 24 to 35 in 9907977
|
Funny, but BIP-39 specification allows empty passwords.
Anyway, it's up to you, one more line of code isn't a problem. |
I didn't check BIP-39, sorry. Thanks for info. Validation of passwrod is not needed as we should stick to the standard. :) |
Related: #29 |
Concerning #29, what if we limit maximum password length to... let say 256 UTF-8 characters? |
It happens that for Latin (in particular, English) phrases all is fine; for Japanese (and other non-Latin), though, we have problems. Added some tests in 7310479.
If I don't see the code, I don't know how to break it. Btw, who must check the length of the password? |
During today's lecture, some students asked if they can use PBKDF2 from standard library of Go and from standard library of Java, doc. Švenda told them they cannot -- they have to implement it and they can use only functions for hashes. So I told him that I explicitly asked about Python's PBKDF2 after previous lecture and that it was accepted. The result is there was some misunderstanding and we have to implement PBKDF2. We talked about it and it makes sense, because teams working in pure C would have great disadvantage. Seed generation has to be implemented without Related: #16 |
you could review #36 and then we can merge it :) |
@lsolodkova #36 is already merged. Please have a look at the seed generation. I also updated branch |
I think this can be closed, what about you, @lsolodkova? |
Of course. Looking forward to any bugs and issues:) |
No description provided.
The text was updated successfully, but these errors were encountered: