From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: barebox@lists.infradead.org
Subject: [PATCH 0/8 v2] add sha384/sha512 and hmac support
Date: Wed, 11 Mar 2015 14:38:27 +0100 [thread overview]
Message-ID: <20150311133827.GO30554@ns203013.ovh.net> (raw)
HI,
this will allow to add later secure boot support
This the first patch series of some mores
To add
- AES with CBC and XTS
- RSA with AS1N and X509
- Key store support
- 2 customs software support
- 1 hardware secure boot support
- a generic API to handle secure boot
without specific user interaction
v2:
switch hmac to a generic digest as hmac(%s) such as hamc(sha256)
add set_key to algo to allow to pass the key
RSA_SIGN will be intergrate in the same way
for the command use -h to pass the key (similar to openssl)
The following changes since commit a1a5a212985053fac141975f6f6cd8e30051b401:
Documentation: handle missing group declaration (2015-03-10 15:04:23 +0100)
are available in the git repository at:
git://git.jcrosoft.org/barebox.git delivery/hmac
for you to fetch changes up to b92e8460facf9bc65ec511a44a305e4273a31d70:
command: add hmac sum supportfor md5, sha1, sha224, sha256, sha384, sha512 (2015-03-11 18:45:59 +0800)
----------------------------------------------------------------
Jean-Christophe PLAGNIOL-VILLARD (8):
digest: move digest.c to crypto
digest: introduce digest_{init/update/final/length}
digest: make it multi-instance
crypto: add sha384 & sha512 support
command: add sha384sum and sha512sum support
password: add support for sha512
digest: add HMAC support for md5, sha1, sha224, sha256, sha384, sha512
command: add hmac sum supportfor md5, sha1, sha224, sha256, sha384, sha512
commands/Kconfig | 24 +++++++++++++
commands/digest.c | 81 ++++++++++++++++++++++++++++++++++++++----
common/Kconfig | 4 +++
common/Makefile | 1 -
common/password.c | 33 +++++++++--------
crypto/Kconfig | 9 +++++
crypto/Makefile | 4 +++
{common => crypto}/digest.c | 64 +++++++++++++++++++++++++--------
crypto/hmac.c | 129 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
crypto/internal.h | 15 ++++++++
crypto/md5.c | 42 ++++++++++------------
crypto/sha1.c | 42 ++++++++++------------
crypto/sha2.c | 92 +++++++++++++++++++++++------------------------
crypto/sha4.c | 361 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
include/digest.h | 50 +++++++++++++++++++++++---
15 files changed, 815 insertions(+), 136 deletions(-)
rename {common => crypto}/digest.c (68%)
create mode 100644 crypto/hmac.c
create mode 100644 crypto/internal.h
create mode 100644 crypto/sha4.c
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2015-03-11 13:39 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=20150311133827.GO30554@ns203013.ovh.net \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.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