From: Alexander Tereschenko <aleksandr.v.tereschenko@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Security Working Group meeting - this Wednesday February 19 - summary results
Date: Fri, 21 Feb 2020 13:19:25 +0100 [thread overview]
Message-ID: <2b30dde7-3415-8c7a-2001-28793e938339@linux.intel.com> (raw)
In-Reply-To: <20200220162633.GB41328@patrickw3-mbp.dhcp.thefacebook.com>
On 20-Feb-20 17:26, Patrick Williams wrote:
> Can we put something into bmcweb to detect its own
> certificate has expired and generate a new one?
The idea here is to discourage any prolonged use of the default
self-signed certs at all, as they don't provide full protection from
MitM attacks. That's why the 30 days validity period was suggested
(compared to current 10 years) and discussed during the meeting. Adding
an auto-regeneration feature would be going directly against that idea,
so I personally wouldn't vote for that.
> I know self-signed certs aren't great, but the minute I have more than 6
> systems I'm not going to want to follow some "BMC Admin Guide" to update
> certificates by hand. So we're effectively forcing everyone to develop
> some kind of certificate management infrastructure, without providing
> (or pointing to an existing) implementation.
I'd say that in such context, you'd be using one of the configuration
management systems (Puppet/Chef/Salt/Ansible/homegrown scripts/whatnot)
anyway, as that's a standard system administration BKM, so IMHO that's a
reasonable assumption at the OpenBMC project end that it's not going to
add any noticeable burden for BMC admins.
next prev parent reply other threads:[~2020-02-21 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 22:29 Security Working Group meeting - this Wednesday February 19 Joseph Reynolds
2020-02-19 23:05 ` Security Working Group meeting - this Wednesday February 19 - summary results Joseph Reynolds
2020-02-20 16:26 ` Patrick Williams
2020-02-21 12:19 ` Alexander Tereschenko [this message]
2020-02-21 20:10 ` Patrick Williams
2020-02-21 20:21 ` Bruce Mitchell
2020-02-21 20:26 ` Patrick Williams
2020-02-21 20:29 ` James Feist
2020-02-24 16:19 ` Michael Richardson
2020-02-26 11:58 ` Alexander Tereschenko
2020-02-26 13:34 ` Michael Richardson
2020-02-24 16:14 ` Michael Richardson
2020-03-03 17:56 ` Gunnar Mills
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=2b30dde7-3415-8c7a-2001-28793e938339@linux.intel.com \
--to=aleksandr.v.tereschenko@linux.intel.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.