You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: use user's private key on signature for web session
From now on, the request to register credentials to initiate the
WebSocket connection and open the web terminal no longer receives the
signature of the username. Now, when the fingerprint is sent, we
identify the public key as the session’s authentication method and
require a signature of data sent on the WebSocket connection by the
client. It should be signed with the private key, and the content sent
back to the WebSocket. If the signature matches, the connection
continues as usual.
0 commit comments