From: Roman Pen <r.peniaev@gmail.com>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>,
Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org, Roman Pen <r.peniaev@gmail.com>
Subject: [PATCH 0/2] mmc-utils: RPMB support
Date: Mon, 21 Jul 2014 21:53:43 +0900 [thread overview]
Message-ID: <1405947225-6347-1-git-send-email-r.peniaev@gmail.com> (raw)
This is simple RPMB support for 4 operations:
write-key
read-counter
write-block
read-block
I did not attempt to implement multiple blocks read/write,
thus only 1 block (256 b) is supported right now.
Also I had to take HMAC SHA256 implementation as 3rdparty to
sign RPMB messages.
Roman Pen (2):
mmc-utils: RPMB: add HMAC SHA256 support
mmc-utils: RPMB: add support for 4 rpmb operations
3rdparty/hmac_sha/hmac_sha2.c | 544 ++++++++++++++++++++++++
3rdparty/hmac_sha/hmac_sha2.h | 140 +++++++
3rdparty/hmac_sha/sha2.c | 949 ++++++++++++++++++++++++++++++++++++++++++
3rdparty/hmac_sha/sha2.h | 108 +++++
Makefile | 8 +-
mmc.c | 28 ++
mmc.h | 6 +
mmc_cmds.c | 419 +++++++++++++++++++
mmc_cmds.h | 4 +
9 files changed, 2204 insertions(+), 2 deletions(-)
create mode 100644 3rdparty/hmac_sha/hmac_sha2.c
create mode 100644 3rdparty/hmac_sha/hmac_sha2.h
create mode 100644 3rdparty/hmac_sha/sha2.c
create mode 100644 3rdparty/hmac_sha/sha2.h
--
2.0.0
next reply other threads:[~2014-07-21 12:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 12:53 Roman Pen [this message]
2014-07-21 12:53 ` [PATCH 1/2] mmc-utils: RPMB: add HMAC SHA256 support Roman Pen
2014-07-21 12:53 ` [PATCH 2/2] mmc-utils: RPMB: add support for 4 rpmb operations Roman Pen
2014-08-12 14:25 ` [PATCH v2 " Roman Pen
2014-08-12 14:30 ` Roman Peniaev
2014-08-12 13:33 ` [PATCH 0/2] mmc-utils: RPMB support Ulf Hansson
2014-08-12 13:48 ` Chris Ball
2014-08-12 14:01 ` Roman Peniaev
2014-08-12 14:04 ` Chris Ball
2014-08-12 14:06 ` Roman Peniaev
2014-08-12 14:13 ` Chris Ball
2014-08-12 14:33 ` Roman Peniaev
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=1405947225-6347-1-git-send-email-r.peniaev@gmail.com \
--to=r.peniaev@gmail.com \
--cc=bengardiner@nanometrics.ca \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.