diff options
author | Alon Levy <alevy@redhat.com> | 2010-11-25 10:12:19 +0200 |
---|---|---|
committer | Alon Levy <alevy@redhat.com> | 2010-12-09 13:36:18 +0200 |
commit | abe75061682726f4ee55c7e849340cce2b74b31d (patch) | |
tree | 0f2c21d049e6dca1456fedb07d9f7f244b8142c3 /passthru.h | |
parent | b86ae0a8573bbd1f8e0247fd27b91e8acf91eb1e (diff) |
libcaccard: coding style: whitespace
Diffstat (limited to 'passthru.h')
-rw-r--r-- | passthru.h | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -10,7 +10,7 @@ * the card from the guest side, and thus does not try to get locks. This means * client access can interfere with the guest use of the card. 2) passthru does * not provide the guest and client unique login states for the card. That - * means that it is possible for the guest to access private data on the + * means that it is possible for the guest to access private data on the * card without authenticating. You have been warned. * * Passthru is most useful in the following cases: 1) provisioning. Card type |