From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] RSA in U-Boot
Date: Thu, 16 May 2019 20:56:40 +0900 [thread overview]
Message-ID: <20190516115636.GA8052@fireball> (raw)
In-Reply-To: <20190516111359.GQ22232@bill-the-cat>
Hi Tom,
On Thu, May 16, 2019 at 07:13:59AM -0400, Tom Rini wrote:
> On Thu, May 16, 2019 at 01:45:54PM +0300, Ilias Apalodimas wrote:
> > On Thu, May 16, 2019 at 12:39:02PM +0200, Wolfgang Denk wrote:
> > Hello Wolfgang,
> >
> > Thanks for taking the time with this
> > > >
> > > > There is LibreSSL as well which is a fork of openssl. Guess that too should
> > > > be fine. What would be the more preferred solution here. The relevant bits
> > > > can be imported from the kernel code into u-boot, or there can be a
> > > > solution with linking of ssl/tls library with u-boot. Which would be the
> > > > more preferred solution. It'd be great if the maintainers can comment on
> > > > this. Thanks.
> > >
> > > I'd go for the Linux kernel code. A number of issues we have here
> > > (cross compiling, code size, license compatibility, long term
> > > maintenance efforts) have already been considered there, so why
> > > should we duplicate all these efforts? And if we did, is there any
> > > clear benefit from doing this?
> > Well someone has to port the linux code in U-Boot and maintain it though.
> >
> > The LibreSSL proposal was made with some of these in mind.
> > We don't expect the licence to ever change (which is compatible)
> > and it's being maintained.
> > I am not sure on the portability status, but i think it runs on all major
> > architectures.
> >
> > I'd imagine this lifts the maintenance burden from U-Boot. On the other
> > hand we'll rely on an external library to offer the functionality.
>
> I don't see how using LibreSSL instead of Linux kernel code would have a
> lesser maintenance burden, sorry. If anything, given the number of
> parts of the code we have today that come from the Linux kernel, adding
> one more to the "keep in sync, or at least port bugfixes" list is less
> than "add a new external project to keep an eye on".
# I will reply on this topic in more details tomorrow.
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?
Thanks,
-Takahiro Akashi
> --
> Tom
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
next prev parent reply other threads:[~2019-05-16 11:56 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 [this message]
2019-05-16 12:07 ` Tom Rini
2019-05-16 12:18 ` Wolfgang Denk
2019-05-17 0:12 ` AKASHI Takahiro
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=20190516115636.GA8052@fireball \
--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.