openbmc.lists.ozlabs.org archive mirror
 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: Security Working Group meeting - Wednesday September 29
Date: Mon, 04 Oct 2021 17:49:58 -0400	[thread overview]
Message-ID: <17785.1633384198@localhost> (raw)
In-Reply-To: <e6dbbca0-e4f7-2e0f-146b-e57008a788e9@linux.ibm.com>

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


Joseph Reynolds <jrey@linux.ibm.com> wrote:
    > Can we use consider SRP (dropped in OpenSSL 3.0 -- why?) or other
    > implementations such as GnuTLS?

I meant to add/ask:

I assume OpenSSL is part of the build process today.
Would switching to GnuTLS, WolfTLS or MbedTLS really be possible?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


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

  parent reply	other threads:[~2021-10-04 21:50 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
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   ` Michael Richardson [this message]
2021-10-04 22:08     ` Security Working Group meeting - Wednesday September 29 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=17785.1633384198@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).