All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Joseph Reynolds <jrey@linux.ibm.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: SPAKE, DTLS and passwords
Date: Tue, 05 Oct 2021 11:09:21 -0400	[thread overview]
Message-ID: <27674.1633446561@localhost> (raw)
In-Reply-To: <edfa6abd-e2a2-00ca-3154-59fee4ae125f@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]


Joseph Reynolds <jrey@linux.ibm.com> wrote:
    > On 10/4/21 4:47 PM, Michael Richardson wrote:
    >> Joseph Reynolds <jrey@linux.ibm.com> wrote:
    >> > The planned IPMI over DLTS function will have certificate-based
    >> > authuentication.
    >>
    >> Do you mean that the server will be authenticated with a certificate, or that
    >> it will use mutual authentication?

    > I understand this means mutual-TLS.
    > Based on the gerrit design:
    > https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/31548/4/designs/ipmi-over-dtls.md

So, why is a password needed?

    > Note that design also says the server will have an identity certificate; same
    > as the HTTPS certificate described in
    > https://github.com/openbmc/bmcweb/blob/master/README.md


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2021-10-05 15:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29  1:35 Security Working Group meeting - Wednesday September 29 Joseph Reynolds
2021-10-04 15:15 ` Joseph Reynolds
2021-10-04 21:47   ` SPAKE, DTLS and passwords Michael Richardson
2021-10-05 14:50     ` Joseph Reynolds
2021-10-05 15:09       ` Michael Richardson [this message]
2021-10-05 16:22         ` Joseph Reynolds
2021-10-05 15:24     ` SPAKE, DTLS and passwords + aPAKE and SCRAM Joseph Reynolds
2021-10-13 20:51       ` Vernon Mauery
2021-10-13 20:51     ` SPAKE, DTLS and passwords Vernon Mauery
2021-10-04 21:49   ` Security Working Group meeting - Wednesday September 29 Michael Richardson
2021-10-04 22:08     ` Bruce Mitchell

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=27674.1633446561@localhost \
    --to=mcr@sandelman.ca \
    --cc=jrey@linux.ibm.com \
    --cc=openbmc@lists.ozlabs.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 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.