linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Ball <chris@printf.net>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Roman Pen <r.peniaev@gmail.com>,
	Ben Gardiner <bengardiner@nanometrics.ca>,
	linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 0/2] mmc-utils: RPMB support
Date: Tue, 12 Aug 2014 14:48:05 +0100	[thread overview]
Message-ID: <86egwl7rai.fsf@void.printf.net> (raw)
In-Reply-To: <CAPDyKFoE5Bxn_6wojSbECnUrzNQM4C1i++ye_ApkwovvJYsTFA@mail.gmail.com> (Ulf Hansson's message of "Tue, 12 Aug 2014 15:33:53 +0200")

Hi,

On Tue, Aug 12 2014, Ulf Hansson wrote:
> On 21 July 2014 14:53, Roman Pen <r.peniaev@gmail.com> wrote:
>> 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
>
> This seems like great stuff for mmc-utils. Chris, can you pick them up?

Thanks, pushed to mmc-utils.  I added the following text to the top of
each hmac_sha file:

+ * Since this code has been incorporated into a GPLv2 project, it is
+ * distributed under GPLv2 inside mmc-utils.  The original BSD license
+ * that the code was released under is included below for clarity.

.. since my understanding is that BSD code that's linked into a GPLv2
binary "becomes GPL" inside that project.

- Chris.
-- 
Chris Ball   <http://printf.net/>

  reply	other threads:[~2014-08-12 13:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 12:53 [PATCH 0/2] mmc-utils: RPMB support Roman Pen
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 [this message]
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=86egwl7rai.fsf@void.printf.net \
    --to=chris@printf.net \
    --cc=bengardiner@nanometrics.ca \
    --cc=linux-mmc@vger.kernel.org \
    --cc=r.peniaev@gmail.com \
    --cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).