Now that we have signedIdentityKeysBlobSelector, we can use it in TraditionalLoginForm and SIWELoginForm (next diff) to simplify things.
Details
- Try to log in from web.
- Set breakpoint in loginResponder and make sure signedIdentityKeysBlob comes through and is validated as expected.
- Check the cookies table to see if signed_identity_keys column is populated correctly.
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
web/selectors/socket-selectors.js | ||
---|---|---|
63–64 | This seems like a really significant change. Tons of questions pop up...
Looking at the MySQL database on my personal keyserver, it appears like "Public" has been included previously, so perhaps this is just you fixing up an error that never got to prod? (I hope so...) Separately, high-level meta-point: you should really expect your reviewer to call you out for things like this. It will save everyone some time if you annotate changes like this ahead-of-time. |
web/selectors/socket-selectors.js | ||
---|---|---|
63–64 |
No
The keys in Redux CryptoStore are primaryIdentityKeys and notificationIdentityKeys. Those can be changed in a migration to primaryIdentityPublicKeys and notificationIdentityPublicKeys for consistency. I have a diff locally to make this exact change.
Yes, this was an issue that was caught locally and never got to prod. The selector is being used for the first time in this diff and the issue was found in the course of testing thanks to the validators on the keyserver side.
Sure |
Cool, glad it never reached prod. Don't care about Redux vs. MySQL consistency (personally)