Prototypes LecternP21 · Course player
The server

What the course’s server holds

The learners’ passkeys, every quiz attempt, the certificates with the start of their signatures, and the public key that checks them, read every 2 seconds. The answers to the quizzes are on the server only.

Quiz attempts

LearnerLessonScorePassedTime

Certificates

CodeLearnerIssuedScoreSignature

Passkeys

PasskeyLearnerSignatureCounter

Every route

MethodRouteWhoWhat it does
How Lectern is built
  1. A learner joins with a name and a passkey. The server checks the passkey as the club in P15 does, and keeps a session in a cookie the page cannot read.
  2. A lesson counts as read when its end has been on the screen. The page tells the server, and the server stores it for the learner.
  3. The quiz opens after its lesson is read. The page sends the answers, and the server grades them from its own copy. The page never receives the right answers, only whether each one was right and why.
  4. When every quiz is passed the server issues one certificate per learner. It signs the code, the name, the course, the date and the score with an Ed25519 key that stays on the server.
  5. The PDF is made in the browser with the PDF writer from P10, with Inter embedded. It holds the code, a link and a QR code to the page that checks it.
  6. The check page fetches the certificate by its code and verifies the signature in the browser with the public key, so a certificate that was changed fails.