vincenzopalazzo
/
arti
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

rpc: Clarify how authentication works.

This commit is contained in:
Nick Mathewson 2023-05-15 16:27:53 -04:00
parent c89fac9c3c
commit 9c7680d1f8
1 changed files with 5 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/dev/notes/rpc-meta-draft.md
View File

@ -500,17 +500,12 @@ while concurrently reading arti's replies.
## Authentication
When a connection is first opened,
only authentication requests may be use
until authentication is successful.
only a single "connection" object is available.
Its object ID is "`connection`".
The client must authenticate to the connection
in order to receive any other object IDs.
> TODO: Perhaps it would be a good idea to say
> that when a connection is opened,
> there is an authentication Object (not a session Object)
> and only _that Object_ can be used
> until one of its responses eventually gives the application
> a session Object?
The authentication schemes are:
The pre-authentication methods available on a connection are:
auth:get_proto
: Ask Arti which version of the protocol is in use.