From: Patrick Williams <patrick@stwcx.xyz>
To: Joseph Reynolds <jrey@linux.ibm.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Security Working Group meeting - Wednesday March 16 - results
Date: Wed, 16 Mar 2022 18:21:45 -0500 [thread overview]
Message-ID: <YjJxCRUZQD1HcRXF@heinlein> (raw)
In-Reply-To: <fcc5d68f-a8d7-e857-370d-d1bf9971d018@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
On Wed, Mar 16, 2022 at 12:51:11PM -0500, Joseph Reynolds wrote:
> 1 Please review the phosphor audit design
> https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/46023
> <https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/46023>and related
> code under https://github.com/openbmc/phosphor-logging
> <https://github.com/openbmc/phosphor-logging>directory phosphor-audit.
>
> IBM is interested in working on this.
Was there any feedback on the design? The current proposal seems very
foundational, like phosphor-logging itself, so I want to make sure we have broad
consensus on it before we invest a lot of effort in this approach.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-16 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 2:45 Security Working Group meeting - Wednesday March 16 Joseph Reynolds
2022-03-16 17:51 ` Security Working Group meeting - Wednesday March 16 - results Joseph Reynolds
2022-03-16 19:45 ` Michael Richardson
2022-03-18 22:23 ` Security Working Group meeting - Wednesday March 16 - results - audit log handling Joseph Reynolds
2022-03-16 23:21 ` Patrick Williams [this message]
2022-03-18 22:49 ` Security Working Group meeting - Wednesday March 16 - results Joseph Reynolds
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=YjJxCRUZQD1HcRXF@heinlein \
--to=patrick@stwcx.xyz \
--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.