This is currently a draft of text to be included for registration and authentication. In terms of eventual placement, it may be good to include the registration.md text in the same document that covers the other operations the client can take (apart from authenticate, as this is handled separately).
There are many TODOS that need to be filled in OR linked to new issues. Mostly the former, I think.
This draft
take a very conservative approach to session handling: one request per session. This is obviously not an ideal choice for the final system, but I think for the PoC this is a reasonable (and temporary) default.
does not attempt to write out the individual OPAQUE protocol flows.
This is currently a draft of text to be included for registration and authentication. In terms of eventual placement, it may be good to include the registration.md text in the same document that covers the other operations the client can take (apart from authenticate, as this is handled separately).
There are many TODOS that need to be filled in OR linked to new issues. Mostly the former, I think.
This draft
Closes #11. Closes #10.