version 0.9.2

[pam_pcsc_cr.git] / README.md

diff --git a/README.md b/README.md
index e1527259c42ea40c5399f46e6f1b2269e3a4b38b..d7b91ac118ca5b07fcf2d410cf99a8fe0d8d1c0b 100644 (file)
--- a/README.md
+++ b/README.md
@@ -73,6 +73,9 @@ period. The downside is that if the token is used against multiple
 hosts, and one of them leaks the secret to an adversary, all hosts are
 compromised. This is not the case with the first approach.
 
+The particular data structure is outlined in the picture:
+![](auth-data-structure.svg)
+
 ## Module Operation
 
 Authentication file, containing nonce, encrypted shared secret,
@@ -112,7 +115,7 @@ The only backend option existing is "ykneo:slot=1" or "ykneo:slot=2".
 Slot 2 is the default. Secret must be supplied when creating the file,
 and when modifying the file in the absense of the token. Password is
 used to construct the challenge. If not supplied empty string is used.
-The pam module also used empty string when given "noaskpass" argument,
+The pam module also uses empty string when given "noaskpass" argument,
 so this can be used for "one factor" authentication mode with token
 only. Payload is a string that can be optionally injected as the PAM
 authentication token after successful authentication; subsequent PAM