Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1457264 > unrolled thread
| Started by | Pavel Machek <pavel@ucw.cz> |
|---|---|
| First post | 2016-08-05 22:10 +0200 |
| Last post | 2016-08-05 22:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v5 0/8] Replay Protected Memory Block (RPMB) subsystem Pavel Machek <pavel@ucw.cz> - 2016-08-05 22:10 +0200
| From | Pavel Machek <pavel@ucw.cz> |
|---|---|
| Date | 2016-08-05 22:10 +0200 |
| Subject | Re: [PATCH v5 0/8] Replay Protected Memory Block (RPMB) subsystem |
| Message-ID | <s2TBn-3Q8-7@gated-at.bofh.it> |
Hi! > Few storage technologies such is EMMC, UFS, and NVMe support RPMB > hardware partition with common protocol and frame layout. > The RPMB partition cannot be accessed via standard block layer, but by a > set of specific commands: WRITE, READ, GET_WRITE_COUNTER, and > PROGRAM_KEY. > Such a partition provides authenticated and replay protected access, > hence suitable as a secure storage. ...and that is suitable from locking devices from their owners, as Nokia N9 (aka brick, because Microsoft turned off support servers) teached me recently. So I have to ask -- what are non-evil uses for this? There were "secure extensions" mentioned before, but my understanding is that it currently has severe limitations making it unsuitable for mainline kernel. (IOW you can't event test the functionality if you are not Intel). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Back to top | Article view | linux.kernel
csiph-web