From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] RSA in U-Boot
Date: Fri, 17 May 2019 09:12:07 +0900 [thread overview]
Message-ID: <20190517001206.GX11160@linaro.org> (raw)
In-Reply-To: <20190516121803.C6216245E45@gemini.denx.de>
Tom, Wolfgang,
Thank you for your inputs.
On Thu, May 16, 2019 at 02:18:03PM +0200, Wolfgang Denk wrote:
> Dear Akashi Takahiro,
>
> In message <20190516115636.GA8052@fireball> you wrote:
> >
> > Can you give me an example of U-Boot code which comes from linux (or
> > other projects) and is regularly synced (or updated) with the origin?
> > Who maintains that? and how?
>
> Comes from Linux: a ton... Kconfig, Linker Script, MTD, UBI, UBIFS,
> ext2/3/4, jffs2, libfdt, many drivers, network stack,
> reiserfs, just to name a few.
>
> Regularly synced: None. Usually this only happens in irregular
> intervals, if incompatibilities or bugs (that have been
> fixed in more recent code) show up
>
> Who: usually the responsible custodians
"Custodians" don't always mean sub-system maintainers. Right?
> How: ideally thius should be a straightforward, though largely
> manual process.
In fact, I have already imported relevant kernel code into U-Boot
and it now works perfectly with my experimental UEFI secure boot patch,
but see the total size (and numbers) of files imported is quite big.
I wonder who is willing to maintain them:
cmd/Kconfig | 3 +
include/crypto/internal/rsa.h | 65 ++
include/crypto/pkcs7.h | 51 ++
include/crypto/public_key.h | 88 ++
include/linux/asn1.h | 69 ++
include/linux/asn1_ber_bytecode.h | 93 +++
include/linux/asn1_decoder.h | 24 +
include/linux/oid_registry.h | 103 +++
include/u-boot/rsa-mod-exp.h | 3 +
lib/Kconfig | 12 +
lib/Makefile | 18 +
lib/asn1_decoder.c | 518 ++++++++++++
lib/build_OID_registry | 207 +++++
lib/crypto/Kconfig | 16 +
lib/crypto/Makefile | 38 +
lib/crypto/pkcs7.asn1 | 135 ++++
lib/crypto/pkcs7_parser.c | 701 ++++++++++++++++
lib/crypto/pkcs7_parser.h | 69 ++
lib/crypto/public_key.c | 340 ++++++++
lib/crypto/rsa_helper.c | 81 ++
lib/crypto/rsapubkey.asn1 | 4 +
lib/crypto/x509.asn1 | 60 ++
lib/crypto/x509_akid.asn1 | 35 +
lib/crypto/x509_cert_parser.c | 681 ++++++++++++++++
lib/crypto/x509_parser.h | 72 ++
lib/crypto/x509_public_key.c | 277 +++++++
lib/oid_registry.c | 170 ++++
lib/rsa/Kconfig | 7 +
lib/rsa/Makefile | 2 +-
lib/rsa/rsa-keyprop.c | 631 +++++++++++++++
lib/rsa/rsa-verify.c | 59 +-
scripts/Makefile | 3 +
scripts/Makefile.build | 6 +-
scripts/asn1_compiler.c | 1615 +++++++++++++++++++++++++++++++++++++
scripts/linux/asn1.h | 69 ++
scripts/linux/asn1_ber_bytecode.h | 93 +++
tools/Makefile | 2 +
37 files changed, 6409 insertions(+), 11 deletions(-)
My modification is not yet optimized to keep updates much easier,
but those numbers will give you a rough idea.
Thanks,
-Takahiro Akashi
next prev parent reply other threads:[~2019-05-17 0:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 2:17 [U-Boot] RSA in U-Boot AKASHI, Takahiro
2019-04-25 2:12 ` AKASHI, Takahiro
2019-04-26 9:05 ` Alexander Graf
2019-04-26 20:16 ` Laszlo Ersek
2019-04-27 5:31 ` Paolo Bonzini
2019-04-27 6:33 ` Heinrich Schuchardt
2019-05-16 7:23 ` Sughosh Ganu
2019-05-16 10:39 ` Wolfgang Denk
2019-05-16 10:45 ` Ilias Apalodimas
2019-05-16 11:13 ` Tom Rini
2019-05-16 11:19 ` Ilias Apalodimas
2019-05-16 11:56 ` AKASHI Takahiro
2019-05-16 12:07 ` Tom Rini
2019-05-16 12:18 ` Wolfgang Denk
2019-05-17 0:12 ` AKASHI Takahiro [this message]
2019-05-17 8:47 ` Wolfgang Denk
2019-05-22 5:48 ` AKASHI Takahiro
2019-06-05 5:27 ` AKASHI Takahiro
2019-06-05 14:04 ` Tom Rini
2019-08-27 10:35 ` Grant Likely
2019-08-27 23:55 ` AKASHI Takahiro
2019-05-16 17:57 ` Paolo Bonzini
2019-05-17 0:26 ` AKASHI, Takahiro
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=20190517001206.GX11160@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
/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.