AtHeartEngineer/specs
1
0
Fork 0
mirror of https://github.com/vacp2p/specs.git synced 2026-01-10 07:47:59 -05:00
Code Issues Packages Projects Releases Wiki Activity

Allow for using an server-encrypted value as challenge-client

Browse Source
This commit is contained in:
Marco Munizaga
2023-08-07 16:53:53 -07:00
parent 43a1c721cc
commit abd08f2ed5
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
http/peer-id-auth.md
View File

@@ -19,8 +19,9 @@ challenge-response scheme. The authentication scheme is called `Libp2p-PeerID``
1. The server initiates the authentication by responding to a request that must
be authenticated with the response header `WWW-Authenticate: Libp2p-PeerID
challenge-client="<base64-encoded-challenge>`. The challenge MUST be randomly
generated from server for sole purpose of authenticating the client. The
challenge-client="<base64-encoded-challenge>`. The challenge MUST be
indistinguishable from random data. The Server MAY randomly generate this
data, or MAY use an server-encrypted value. If using random data the
server SHOULD store the challenge temporarily until the authentication is
done. The challenge SHOULD be at least 32 bytes.