From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: openbmc <openbmc@lists.ozlabs.org>, Joseph Reynolds <jrey@linux.ibm.com>
Subject: Re: Security Working Group meeting - Wednesday August 31 - results
Date: Thu, 1 Sep 2022 08:41:53 -0400 [thread overview]
Message-ID: <20220901124153.ofhmyymhcra34akr@cheese> (raw)
In-Reply-To: <YxCWpNZ+O89B+ulA@heinlein.stwcx.org.github.beta.tailscale.net>
On Thu, Sep 01, 2022 at 06:25:24AM -0500, Patrick Williams wrote:
>written entirely in Python, which makes it very difficult for us to support
>on any of the NOR-based systems (all of them except IBM's latest).
Is the suggestion that they rewrite it in C++ and contribute that? If
it is, why would they invest in building a project and community from
scratch as opposed to using an existing one just because all the other
in-tree servers are hyper-cost optimized?
next prev parent reply other threads:[~2022-09-01 12:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 1:08 Security Working Group meeting - Wednesday August 31 Joseph Reynolds
2022-08-31 1:16 ` Security Working Group meeting - Wednesday August 31 - new venue Joseph Reynolds
2022-08-31 18:09 ` Security Working Group meeting - Wednesday August 31 - results Joseph Reynolds
2022-09-01 11:25 ` Patrick Williams
2022-09-01 12:41 ` Brad Bishop [this message]
2022-09-01 15:07 ` Patrick Williams
2022-09-05 19:04 ` Joseph Reynolds
2022-09-01 21:23 ` Michael Richardson
2022-09-02 16:07 ` Thore Sommer
2022-09-06 13:10 ` Patrick Williams
2022-09-05 18:56 ` Joseph Reynolds
2022-09-06 8:05 ` Michael Richardson
2022-09-06 13:09 ` Patrick Williams
2022-09-12 19:31 ` George Almasi
2022-09-06 13:07 ` Patrick Williams
2022-09-07 8:01 ` Michael Richardson
2022-09-01 11:27 ` Patrick Williams
2022-09-05 18:59 ` Joseph Reynolds
2022-09-06 20:16 ` Patrick Williams
2022-09-08 18:57 George Almasi
[not found] ` <101586.1662709990@dooku>
2022-09-09 18:49 ` George Almasi
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=20220901124153.ofhmyymhcra34akr@cheese \
--to=bradleyb@fuzziesquirrel.com \
--cc=jrey@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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.