anchor.diff:  configuration. 
   
   
  -=== Testing the Configuration ===
  +== Testing the Configuration ==
   
   We assume that you have 'root' and 'test' user configured to access SSH on your
   test environment with password 'secret' and 'pencil' respectively. 
  
positive.code: Yubico PAM Version:: pam_yubico-1.7
  
  
  ==== PAM configuration ====
  
  PAM configuration files in our testing environment are as follows:
  
  
  ===== /etc/pam.d/sshd =====
  -------
  auth           required  	 pam_yubico.so authfile=/etc/yubikeyid id=16 debug
  auth           include   	 system-auth
  
negative.code: to the user.
  
  
  == Build yubico-c-client and pam_yubico ==
  
  Build instructions for yubico-c-client and pam_yubico are found in their
  respective README.
  
  
  == Configuration ==
  
  === Configuration for user and YubiKey token ID mapping ===
  
  There are two ways of user and YubiKey token ID mapping. It can be either
  done at administrative level or at individual user level.
  
  ==== Administrative Level ====
  
  In Administrative level, system administrators hold right to configure the
  user and yubikey token ID mapping. Administrators can achieve this by creating
  