diff options
| author | 46halbe <46halbe@berlin.ccc.de> | 2013-09-22 18:25:13 +0000 |
|---|---|---|
| committer | 46halbe <46halbe@berlin.ccc.de> | 2020-05-23 13:39:30 +0000 |
| commit | fb37ce8b748f287e0a0f5cf56471daa7dbe72da6 (patch) | |
| tree | e260eea9e2faf4d3e40aea3d937b338f69e61159 | |
| parent | b8c64ad742eedf02640cba4de4bc76229c29ce65 (diff) | |
committing page revision 2
| -rw-r--r-- | updates/2013/ccc-breaks-apple-touchid.en.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/updates/2013/ccc-breaks-apple-touchid.en.md b/updates/2013/ccc-breaks-apple-touchid.en.md index 61dfe186..63890204 100644 --- a/updates/2013/ccc-breaks-apple-touchid.en.md +++ b/updates/2013/ccc-breaks-apple-touchid.en.md | |||
| @@ -1,8 +1,8 @@ | |||
| 1 | title: Chaos Computer Club breaks Apple TouchID | 1 | title: Chaos Computer Club breaks Apple TouchID |
| 2 | date: 2013-09-21 22:04:00 | 2 | date: 2013-09-21 22:04:00 |
| 3 | updated: 2013-09-22 18:11:56 | 3 | updated: 2013-09-22 18:25:13 |
| 4 | author: frank | 4 | author: frank |
| 5 | tags: update, pressemitteilung, biometrie, biometrics, apple, touchid | 5 | tags: update, pressemitteilung, biometrie, biometrics, apple, touchid, fingerprint |
| 6 | 6 | ||
| 7 | The biometrics hacking team of the Chaos Computer Club (CCC) has successfully bypassed the biometric security of Apple's TouchID using easy everyday means. A fingerprint of the phone user, photographed from a glass surface, was enough to create a fake finger that could unlock an iPhone 5s secured with TouchID. This demonstrates – again – that fingerprint biometrics is unsuitable as access control method and should be avoided. | 7 | The biometrics hacking team of the Chaos Computer Club (CCC) has successfully bypassed the biometric security of Apple's TouchID using easy everyday means. A fingerprint of the phone user, photographed from a glass surface, was enough to create a fake finger that could unlock an iPhone 5s secured with TouchID. This demonstrates – again – that fingerprint biometrics is unsuitable as access control method and should be avoided. |
| 8 | 8 | ||