From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-man@vger.kernel.org, linux-sgx@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
nathaniel@profian.com, Michael Kerrisk <mtk.manpages@gmail.com>,
Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: [PATCH v11] sgx.7: New page with overview of Software Guard eXtensions (SGX)
Date: Fri, 31 Mar 2023 00:29:06 +0200 [thread overview]
Message-ID: <623b0792-3bf2-271a-d451-4d4e683ce662@gmail.com> (raw)
In-Reply-To: <YhKfA87I0BbkLg+m@iki.fi>
[-- Attachment #1.1: Type: text/plain, Size: 1664 bytes --]
Hi Jarkko,
I was revisiting old mails, and found this thread that seems unresolved.
Do you still have the page around and want to send it?
Cheers,
Alex
On 2/20/22 21:05, Jarkko Sakkinen wrote:
> On Wed, Feb 09, 2022 at 09:19:54PM +0100, Alejandro Colomar (man-pages) wrote:
>> Hi Jarkko,
>>
>> On 1/28/22 02:19, Jarkko Sakkinen wrote:
>>> On Fri, Dec 17, 2021 at 02:50:56AM +0100, Alejandro Colomar (man-pages) wrote:
>>>> Hi Jarkko,
>>>>
>>>> Please see some comments below.
>>>>
>>>> Thanks,
>>>> Alex
>>>
>>> Thank you. I've addressed all the comments below. However, I feel that
>>> /dev/sgx_provision is not properly documented at all. I also think that
>>> Reinette's argument for v10 was fair that "remove VEPC" ioctl that QEMU
>>> uses should not be left out from the initial patch set.
>>>
>>> I'm implementing user space that doest attestation, so I rather write a
>>> proper description of the attestation, once it is working, rather than add
>>> to the number of review rounds.
>>
>> Fair enough. Please send an v12 with those comments addressed, and I'll
>> merge it! (if you miss anything, we'll fix it later, don't worry)
>
> It took me two weeks to do the remote attestation implementation for Enarx
> project [*] but I needed to do it before continuing with the man page. I'll
> continue with this some time next week. It's not exactly directly attached
> to kernel API but I think it is good to bring some context on that.
>
> [*] https://github.com/enarx/enarx/pull/1329
>
> BR, Jarkko
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-30 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 15:33 [PATCH v11] sgx.7: New page with overview of Software Guard eXtensions (SGX) Jarkko Sakkinen
2021-12-17 1:50 ` Alejandro Colomar (man-pages)
2022-01-28 1:19 ` Jarkko Sakkinen
2022-02-09 20:19 ` Alejandro Colomar (man-pages)
2022-02-20 20:05 ` Jarkko Sakkinen
2023-03-30 22:29 ` Alejandro Colomar [this message]
2023-04-21 21:13 ` Jarkko Sakkinen
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=623b0792-3bf2-271a-d451-4d4e683ce662@gmail.com \
--to=alx.manpages@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=nathaniel@profian.com \
--cc=reinette.chatre@intel.com \
/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).