anchor.diff:  -------
   
   
  -* /etc/yubikeyid:
  -
  --------
  -    root:indvnvlcbdre:ldvglinuddek
  -    test:ldvglinuddek
  --------
  -
  -* /root/.yubico/authorized_yubikeys:
  -
  --------
  -    root:indvnvlcbdre:ldvglinuddek
  +===== /etc/yubikeyid =====
  +
  +-------
  +root:indvnvlcbdre:ldvglinuddek
  +test:ldvglinuddek
  +-------
  +
  +===== /root/.yubico/authorized_yubikeys =====
  +
  +-------
  +root:indvnvlcbdre:ldvglinuddek
   -------
   
   Please change PAM configuration settings for SSH as shown above and test the
  
positive.code: === 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. 
   
  Use any standard SSH client for testing (We used SSH command line utility).   
  
  
negative.code: 
  ====== Configuration of modified pam_yubico.so module at administrative level ======
  
  Append the following line to the beginning of the `/etc/pam.d/sshd` file:
  
   auth required pam_yubico.so id=16 debug authfile=/path/to/mapping/file
  
  Make sure you set `id=16` to the correct API-id for the yubico validation server.
  
  After the above configuration changes, whenever a user connects to the server
  using any ssh client, the PAM authentication interface will pass the control to
  