3 ms·
From one of the articles linked in the wiki entry: Basically it’s done like this: 1. The server passes a random string to the client 2. The clien
by run4yourlives 18y ago
From one of the articles linked in the wiki entry:
Basically it’s done like this:
1. The server passes a random string to the client
2. The client performs a calculation on the password and the random string
3. The client passes the username (in plain text) and the result of the calculation to the server
4. The server performs the same calculation as the client did and compares the output to the output of the client.
5. If it’s a match, the client is authentic.
- JulianMorrison 18y agoThat's a HMAC password protocol, it's different. In the case of tickets, the one signing is "this server then" and the one checking is "this server now", with a period of amnesia (about the data, not about the password) in between.
- run4yourlives 18y agoAhh, my bad. I think I see where you're going with this now. You're basically just remembering the last visit a particular client makes on every request, and then resetting the ticket for the next request correct?
- JulianMorrison 18y agoImagine a disposable photo-ID ticket marked "admit one authenticated client". The bouncer takes it, looks at it, looks at you, tears it in half, and lets you in. You get to make a request, and as you carry the response out of the exit door, a member of staff takes your photo and prints a fresh ticket.