Security Working Group meeting - Wednesday August 3
This is a reminder of the OpenBMC Security Working Group meeting scheduled for this Wednesday August 3 at 10:00am PDT.
We'll discuss the following items on the agenda <https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI>, and anything else that comes up:
1. Continue discussing CVE response, SELinux, and Measured Boot
2. Recommend http header values per email dated 2022-07-22 with subject: BMCWeb support new HTTP headers Referrer-Policy and Feature-Policy renamed to Permissions-Policy
3. Consider increasing the TLS DH keysize from 1024 to 2048 bits per best practice (reference needed).
4. Consider migrating this meeting access to Discord > Voice channels > Security.
Access, agenda and notes are in the wiki:
https://github.com/openbmc/openbmc/wiki/Security-working-group <https://github.com/openbmc/openbmc/wiki/Security-working-group>
- Joseph
Re: Security Working Group meeting - Wednesday August 3 - results
Quoted 4 lines · Joseph Reynolds
This is a reminder of the OpenBMC Security Working Group meeting scheduled for this Wednesday August 3 at 10:00am PDT.
We'll discuss the following items on the agenda <https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI>, and anything else that comes up:
Quoted 10 lines
1. Continue discussing CVE response, SELinux, and Measured Boot
2. Recommend http header values per email dated 2022-07-22 with subject: BMCWeb support new HTTP headers Referrer-Policy and Feature-Policy renamed to Permissions-Policy
3. Consider increasing the TLS DH keysize from 1024 to 2048 bits per best practice (reference needed).
4. Consider migrating this meeting access to Discord > Voice channels
Quoted 1 line
Security.
Attended:Joseph Reynolds, Russel Wilson, Yutaka Sugawara, Ruud Haring, James Mihm, Dhananjay, Krishnan Sugavanam, Sandhya Koteshwara, James Bottomley, Dick from Phoenix, Chris Engel, Gheorge Almas, Alda Ohmacht.
1 Continue discussing CVE response, SELinux, and Measured Boot
DISCUSSION: (We skipped over the first topic and went to the second topic.)
2 Recommend http header values per email dated 2022-07-22 with subject: BMCWeb support new HTTP headers Referrer-Policy and Feature-Policy renamed to Permissions-Policy.
DISCUSSION:
No discussion. The email archive is https://lore.kernel.org/openbmc/CAH2-KxBuPhrv3bBu3ihr1AW6jpLXWvhr3pY0a4zqdFw0eFKkbw@mail.gmail.com/ <https://lore.kernel.org/openbmc/CAH2-KxBuPhrv3bBu3ihr1AW6jpLXWvhr3pY0a4zqdFw0eFKkbw@mail.gmail.com/>
3 Consider increasing the TLS DH session keysize from 1024 to 2048 bits per best practice (reference needed).
DISCUSSION:
BMCWeb references the OWASP guidelines.
Reference: NIST SP 800-131A recommends DH keysize 2048 bits. This is to protect against a supercomputer cracking the session key.
An alternative defense is to disallow the Diffie Hellman (DH) algorithm and use Elliptic Curve (ECDH).
Note that removing support for DH will break older browsers which don’t support ECDH. Can we increase keysize? Yes, will take more of the limited BMC compute power.
Two of the places which use SSL: BMCWeb, dropbear SSH. To change these would need a configuration or code change to update the key size. Note the BMC creates other SSL connections which also may need similar configuration. See https://github.com/openbmc/docs/blob/master/architecture/interface-overview.md <https://github.com/openbmc/docs/blob/master/architecture/interface-overview.md>.
Tangentially-related topic: Use the AST2600 BMC’s Hash and crypto engine (HACE) engine?
Kernel patch series for AST2600 crypto engine: https://lore.kernel.org/linux-crypto/?q=s%3Ahace <https://lore.kernel.org/linux-crypto/?q=s%3Ahace>; note just has HACE (AES/SHA), no ACRY yet. ASpeed is working on Kernel driver for the ACRY engine for RSA, etc.
New topic: Enhance OpenBMC to enable compliance with NIST FIPS compliance? IBM and Intel are interested in this. Add to applicable standards https://github.com/openbmc/openbmc/wiki/Security-working-group#applicable-standards <https://github.com/openbmc/openbmc/wiki/Security-working-group#applicable-standards>. Next steps: Articulate what FIPS compliance means, and document how the FIPS requirements apply to OpenBMC. Perhaps a design or security doc?
4 Consider migrating this meeting to Discord > Voice channels > Security.
DISCUSSION:
Three responses were: Why? Seems okay. Don’t like Discord.
Access question: Can a web client access the discord voice session?
Also, let’s use the discord #security channel.
The direct link is https://discord.com/channels/775381525260664832/1002376534377635860 <https://discord.com/channels/775381525260664832/1002376534377635860>
We went back to the first topic:
1 Continue discussing CVE response, SELinux, and Measured Boot
DISCUSSION: We only had time for the “CVE Response” subtopic.
Email: Change the OpenBMC project to use github security advisories: https://lore.kernel.org/openbmc/[email protected]/ <https://lore.kernel.org/openbmc/[email protected]/>with gerrit review here: https://gerrit.openbmc.org/c/openbmc/docs/+/55974 <https://gerrit.openbmc.org/c/openbmc/docs/+/55974>
New sub-sub-topic: to help with static scanning tools (scanning either the firmware image file or scan the source code), there is a desire for all OpenBMC repos to have versioning numbers (versus using git commitID). This helps the static source code scan tools report version. Specifically, it helps a security-vulnerability-responder to map from a BMC firmware version back to the list of source package+version used to create that version. This is related to the software bill of materials (SBOM) concept.
The request for repo maintainers is to periodically increment the package version (bitbake PV variable) (either within the recipe or the recipe filename) per best practices (need reference). Examples:
*
Uboot has the package version as part of the recipe filename:
https://github.com/openbmc/openbmc/tree/master/poky/meta/recipes-bsp/u-boot
<https://github.com/openbmc/openbmc/tree/master/poky/meta/recipes-bsp/u-boot>
*
BMCWeb has no branches or tags
(https://github.com/openbmc/bmcweb/tags
<https://github.com/openbmc/bmcweb/tags>) and specifies a generic package version (PV = "1.0+git${SRCPV}") within its recipe
(https://github.com/openbmc/openbmc/blob/master/meta-phosphor/recipes-phosphor/interfaces/bmcweb_git.bb
<https://github.com/openbmc/openbmc/blob/master/meta-phosphor/recipes-phosphor/interfaces/bmcweb_git.bb>)
which merely references the latest bmcweb commit.
James and the security response team to drive this. Is this a question for the Technical Oversight Forum (TOF)?
Next meeting, please cover the Measured boot topic.
Quoted 5 lines
Access, agenda and notes are in the wiki:
https://github.com/openbmc/openbmc/wiki/Security-working-group <https://github.com/openbmc/openbmc/wiki/Security-working-group>- Joseph
Re: Security Working Group meeting - Wednesday August 3 - results
Quoted 8 lines · Joseph Reynolds
4 Consider migrating this meeting to Discord > Voice channels > Security.
DISCUSSION:
Three responses were: Why? Seems okay. Don’t like Discord.
Access question: Can a web client access the discord voice session?
Yes, the web client can access voice sessions. I use the web client exclusively on my work machine.
Quoted 6 lines
Also, let’s use the discord #security channel.
The direct link is
https://discord.com/channels/775381525260664832/1002376534377635860
<https://discord.com/channels/775381525260664832/1002376534377635860>
So from this the outcome of the discussion is a bit unclear.
For better or worse, discord is where a lot of OpenBMC activity takes place. I think something fundamental that the security working group needs to develop is better traction with the OpenBMC (maintainer) community. Problems that are discussed by the Security WG often have direct impacts on maintenance of the software that makes up OpenBMC, most of which the WG attendees are not responsible for.
Migrating the security WG calls to discord will increase regularity of use among WG attendees and hopefully increase interaction with other parts of the OpenBMC community where they need influence.
We already hold weekly Technical Oversight Forum meetings and fortnightly PMCI get-togethers on the respective discord voice channels and it works very well.
IMO Joseph, you should just start hosting the calls on discord. People will move to it if they wish to continue to attend.
Cheers,
Andrew
Re: Security Working Group meeting - Wednesday August 3 - results
Quoted 22 lines · Andrew Jeffery
Quoted 8 lines · Joseph Reynolds
4 Consider migrating this meeting to Discord > Voice channels > Security.
DISCUSSION:
Three responses were: Why? Seems okay. Don’t like Discord.
Access question: Can a web client access the discord voice session?
Yes, the web client can access voice sessions. I use the web client exclusively on my work machine.
Quoted 6 lines
Also, let’s use the discord #security channel.
The direct link is
https://discord.com/channels/775381525260664832/1002376534377635860
<https://discord.com/channels/775381525260664832/1002376534377635860>
Quoted 8 lines
So from this the outcome of the discussion is a bit unclear.
For better or worse, discord is where a lot of OpenBMC activity takes place. I think something fundamental that the security working group needs to develop is better traction with the OpenBMC (maintainer) community. Problems that are discussed by the Security WG often have direct impacts on maintenance of the software that makes up OpenBMC, most of which the WG attendees are not responsible for.
Absolutely, one of the discussions around CVE / GH advisories workflow requires repo maintainers to be involved.
Quoted 4 lines
Migrating the security WG calls to discord will increase regularity of use among WG attendees and hopefully increase interaction with other parts of the OpenBMC community where they need influence.
+1
Quoted 7 lines
We already hold weekly Technical Oversight Forum meetings and fortnightly PMCI get-togethers on the respective discord voice channels and it works very well.
IMO Joseph, you should just start hosting the calls on discord. People will move to it if they wish to continue to attend.
Another issue is current Webex setup is, messages are not accessible after meeting ends, discord channel would solve this offline access?
Thanks,
Dhananjay
Re: Security Working Group meeting - Wednesday August 3 - results
Quoted 6 lines · Dhananjay Phadke
Quoted 5 lines · Andrew Jeffery
We already hold weekly Technical Oversight Forum meetings and fortnightly PMCI get-togethers on the respective discord voice channels and it works very well.
Quoted 6 lines
Quoted 2 lines
IMO Joseph, you should just start hosting the calls on discord. People will move to it if they wish to continue to attend.
Another issue is current Webex setup is, messages are not accessible after meeting ends, discord channel would solve this offline access?
Yeah I think it would based on a quick glance at Joseph having commented in the Security voice channel, though I haven't used the voice channel chat feature yet myself.
Andrew
Re: Security Working Group meeting - Wednesday August 3 - results
Quoted 10 lines · Andrew Jeffery
Quoted 6 lines
Quoted 2 lines
IMO Joseph, you should just start hosting the calls on discord. People will move to it if they wish to continue to attend.
Another issue is current Webex setup is, messages are not accessible after meeting ends, discord channel would solve this offline access?
Yeah I think it would based on a quick glance at Joseph having commented in the Security voice channel, though I haven't used the voice channel chat feature yet myself.
I also made a #security text-only channel.
The voice channel having a chat is a new feature and I don't think most people know to actively look at them. The user interface for it makes it much more difficult to tell that there are even chats to be seen on them. I'd caution against relying on them for content you're expecting people to actively read. You could experiment with them for discussions during the meeting and see if they're useful for that.
Signature · 1 line
Patrick Williams