public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Jiaxin Wu <jiaxin.wu@intel.com>, "Fu, Siyuan" <siyuan.fu@intel.com>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>
Subject: setting the TLS cipher list for HTTPS booting
Date: Fri, 19 Jan 2018 15:33:31 +0100	[thread overview]
Message-ID: <5307d880-d016-ad91-04f5-6b83eb40f905@redhat.com> (raw)

Hello Jiaxin, Siyuan,

it seems that the "preferred set of ciphers" can be controlled at the
TLS session level.

With regard to HTTPS booting, "NetworkPkg/HttpDxe" makes several calls
to EFI_TLS_PROTOCOL.SetSessionData() -- in the file
"NetworkPkg/HttpDxe/HttpsSupport.c", -- but it never passes
"EfiTlsCipherList" as argument for the "DataType" parameter.

Is there a way for platform code to control the list of ciphers?

This is different from other "global" TLS aspects, such as
EFI_TLS_CONFIGURATION_PROTOCOL, because the latter is a singleton
"service" protocol, while EFI_TLS_PROTOCOL instances are created by
clients as-needed, via TLS service binding. So, I think if a platform
wanted to control this on the session level, then it would have to "ask"
HttpDxe somehow.

If you agree -- do you suggest a dynamic PCD, or an extension to the
UEFI spec (at the HTTP level)?

Thanks!
Laszlo


             reply	other threads:[~2018-01-19 14:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 14:33 Laszlo Ersek [this message]
2018-01-20  6:18 ` setting the TLS cipher list for HTTPS booting Wu, Jiaxin
2018-01-22  9:37   ` Laszlo Ersek
2018-01-23  2:43     ` Wu, Jiaxin
2018-01-23 14:01       ` Laszlo Ersek
2018-01-23 15:01         ` Laszlo Ersek
2018-01-24  2:10           ` Wu, Jiaxin
2018-01-24  3:40             ` Wu, Jiaxin
2018-01-24  6:50               ` Wu, Jiaxin
2018-01-24 16:13                 ` Laszlo Ersek
2018-01-25  4:52                   ` Wu, Jiaxin
2018-01-25 12:41                     ` Laszlo Ersek
2018-02-05  3:33                       ` Wu, Jiaxin
2018-02-05 10:46                         ` Laszlo Ersek
2018-02-06  2:34                           ` Wu, Jiaxin

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-list 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=5307d880-d016-ad91-04f5-6b83eb40f905@redhat.com \
    --to=devel@edk2.groups.io \
    /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