Update README.md

pull/33/head
Conor Patrick 2016-06-12 20:15:53 -04:00 zatwierdzone przez GitHub
rodzic 2b88365078
commit e49441dc1e
1 zmienionych plików z 1 dodań i 1 usunięć

Wyświetl plik

@ -21,7 +21,7 @@ Security Overview
The security level is about the same as a car key. Any secret information cannot be read or duplicated. A TRNG is used to generate unpredictable keys.
However, side channel leakage is an unsolved problem in industry and academia. So for well equipped adversaries that can make targetted attacks and get physical access, secret information leakage is possible. Any other hardware token that claims it's "impenetrable" or totally secure are vulnerable to physical side channels and it's important to acknowledge. However, most people don't worry about targeted attacks from well equipped adversaries.
However, side channel leakage is an unsolved problem in industry and academia. So for well equipped adversaries that can make targetted attacks and get physical access, secret information leakage is possible. Any other hardware token that claims it's "impenetrable" or otherwise totally secure are *still* vulnerable to physical side channels and it's important to acknowledge. However, most people don't worry about targeted attacks from well equipped adversaries.
For more information about U2F Zero's secure implementation and the problem of side channels, check out [the wiki](https://github.com/conorpp/u2f-zero/wiki/Security-Overview).