From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Nitrokey Pro not vulnerable to the Nitrokey Start read-only bit
Date: Tue, 30 Apr 2019 17:06:37 +0000 [thread overview]
Message-ID: <robbat2-20190430T165716-885036961Z@orbis-terrarum.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
TL;DR: The Foundation/Nitrokey partnership is sending Nitrokey Pro units
that are not the same as the Nitrokey Start units vulnerable to hands-on
key extraction attack.
As a few people have asked about it:
There was a production batch of "Nitrokey Start" units that did not have
a read-protection bit configured, and thus were vulnerable to a key
extraction attack:
https://github.com/rot42/gnuk-extractor
The issue was specific to a batch of hardware that was mis-programmed,
and the issue is not present on newer Nitrokey Start units.
https://github.com/Nitrokey/nitrokey-start-firmware/issues/14
The Foundation/Nitrokey partnership is providing Nitrokey Pro 2 units,
which are supposedly not vulnerable to this issue (but I'd be happy for
a hardware hacker to confirm this, I understand that the Pro2 has a
seperate smartcard internally)
If you already had an older Nitrokey Start unit, reviewing/updating the
firmware is advised.
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]
reply other threads:[~2019-04-30 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=robbat2-20190430T165716-885036961Z@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox