feedback
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Today
ran -> run
Yesterday
rebase on master
Rebase on master
Address feedback
svc -> keyserver_service
Move prekey information to top-level message
Tue, Mar 21
Expand comment on Sender / Receiver RPCs
Use Sender / Receiver as X3DH roles
not very well versed in gradle, but please add me to cmake related stuff in the future :)
Mon, Mar 20
Fix what information is being requested by whom
Address Feedback
Fri, Mar 17
rlib -> lib
Thu, Mar 16
This currently produces the outpus:
$ du -hd0 --apparent-size pkg/* 715 pkg/comm_opaque.d.ts 160 pkg/comm_opaque.js 14K pkg/comm_opaque_bg.js 142K pkg/comm_opaque_bg.wasm 1005 pkg/comm_opaque_bg.wasm.d.ts 249 pkg/package.json
Add @ashoat because addtion of wasm-pack utility, and new usage of wasm_bindgen crate
Add back rlib for in-repo usage
Add wasm-pack to this diff
Move wasm-pack to wasm diff
Address feedback
Prune stale dependencies
Also assert that session_key was set in test
Remove sever_setup from constructors
Use opaque 2.0, remove server setup
Wed, Mar 15
i'm a little confused why we're moving config.rs and constants.rs into this cargo project. they seem pretty specific to the identity service.
Tue, Mar 14
I might move this code into shared/comm-opaque2, so that we can retain the opaque 1.2 Cipher definition as it is now and avoid having to tackle the migration immediately. Once we trigger the migration, we can just replace the 1.2 code once we are ready to migrate over to opaque 2.0.
Not going tackle updating to 2.0 in this diff, as all downstream usages of comm-opaque::Cipher (which is currently the entire code base) will need to be updated as well.
Expose facade as OOP
Address feedback
Remove stream from update RPC, remove deviceEd27719 fields
opaqueServerResponse -> opaqueLoginResponse
Going to merge into D7022
Rebase on master
Have prekey refresh only pass prekeys and not onetime keys
Mon, Mar 13
Use username or wallet ID for looking up keyserver info
Use userID to find KeyserverInfo
For now, I renamed them all deviceEd25519PublicKey as I think that was the goal initially
signingPublicKey -> deviceEd25519PublicKey
Fix refreshPreKeys message. response -> upload
Split opaque RPCs into two unary RPCs
Correct KeyserverKeysResponse structure
Limit diff to just account actions
Sun, Mar 12
Fri, Mar 10
i don't love adding the dependencies in a separate diff, would like to see them added when they're actually being used
Going to go to a more OOP-like approach instead of some "static methods". Following https://github.com/marucjmar/opaque-wasm as an example of more ergonomic JS bindings.
Rebase on master
Address feedback:
- clarify service comment
- Make LoginPasswordUser into stream, and finalize OPAQUE
- Remove GetUserID (at least for now, until we have a use case)
- signingPublicKey -> deviceEd25519PublicKey
- align opaque message with opaque_ke terms
looks fine to me, not going to accept so that atul can take a look as he's probably more familar with mac workflow.
grpc -> gRPC
Thu, Mar 9
UpdateUser -> UpdateUserPassword
Add comment on rpcs
Use a single "Empty" message instead of rpc specific versions
Wed, Mar 8
Huh wait a user should know their userID, did you guys discard of the concept of a userID entirely because you didn't see it in the whitepaper?