|
Should we have a forum too, like Discourse?
Andy
They tend to be much easier to moderate and follow than mailing lists, but I get that mailing lists are more common among LF projects.
P.S. This is also a test message. |
|
|
|
Re: Should we have a forum too, like Discourse?
Stephano Cetola <scetola@...>
I’ll check on what forum software we use at the LF.
toggle quoted message
Show quoted text
The projects I’ve worked on so far haven’t taken advantage of forums. I do agree though, they can certainly be useful. In that vein, setting up a watch of Stackoverflow posts to alert the list (or whomever) when a new post occurs regarding OESDK is probably wise. I’ll check on how/if we’ve done that in the past as well. I know that Yocto does that, but it notifies their IRC channel. -- Stephano Cetola Program Manager, The Linux Foundation On Nov 16, 2019, at 5:06 PM, Andy <andrew@...> wrote: |
|
|
|
Triage Meeting for Open Enclave SDK
Radhika Jandhyala <radhikaj@...>
Hi everybody,
We would like to invite the Open Enclave SDK community to join us for triage meetings on Tuesdays from 10:00 – 11:00 AM PST. Please use the link/phone number below to join the meeting.
We will go over untriaged issues on https://github.com/openenclave/openenclave.
Thanks, Radhika ________________________________________________________________________________ +1 929-270-4006 United States, New York City (Toll) (866) 641-7188 (Toll-free) Conference ID: 526 582 229#
|
|
|
|
Open Enclave SDK CI Outage
Brett McLaren <Brett.McLaren@...>
Hello Everyone,
This morning an issue has affected the Open Enclave SDK CI/CD taking Windows attestation testing offline. Simulation modes and Linux based testing will still function as expected
but users will not be able to merge PR's until this is resolved. This is being treated as a top priority and we will keep everyone in the loop as the situation progresses until resolution. Everyone’s patience is appreciated at this time.
Thanks,
|
|
|
|
Open Enclave SDK CI Back Up
Brett McLaren <Brett.McLaren@...>
Hello, |
|
|
|
Let's talk about Testing and CI/CD!
Aeva
Hi all,
I'd like to invite everyone who is interested in the topic of Open Enclave's Testing and CI/CD processes to join a call on Tuesday evening. Please pardon any technical hiccups as this will be our first meeting on Zoom. When: 17:30 Tuesday, US West Coast (PDT) 00:30 Wednesday, GMT Zoom link: https://us04web.zoom.us/j/119965269?pwd=bW1GZWJXdWlOb3BldFN5aFFCSTNNQT09 I'll store minutes and notes here: https://hackmd.io/@aeva/oesdk-sig-testing Cheers, Aeva -- Aeva Marie van der Veen Open Source Program Manager Azure Confidential Computing<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fsolutions%2Fconfidential-compute%2F&data=02%7C01%7Caevander%40microsoft.com%7C7fbb53980b99460753b208d7d4c8c6e9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637211831100251112&sdata=2ZiI8CutpXf8h9QU25o7hqOy%2B00JeqaZxcKNyGtKEas%3D&reserved=0> my.pronoun.is/they<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmy.pronoun.is%2Fthey&data=02%7C01%7Caevander%40microsoft.com%7C7fbb53980b99460753b208d7d4c8c6e9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637211831100251112&sdata=KsfcpgHRXKZ9dfdEl8NuDbRIQzcUs%2BozVWYDL9wFhjA%3D&reserved=0> (what’s this?<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.huffpost.com%2Fentry%2Fnon-binary-pronouns-why-they-matter_b_5a03107be4b0230facb8419a&data=02%7C01%7Caevander%40microsoft.com%7C7fbb53980b99460753b208d7d4c8c6e9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637211831100261112&sdata=FVFPUceXrr8ehHJa4E8YH3DToQaEdtZoycWZaNl2F64%3D&reserved=0>) |
|
|
|
Updated Event: Test Event - Please Disregard - Monday, 6 April 2020
#cal-invite
oesdk@lists.confidentialcomputing.io Calendar <oesdk@...>
Test Event - Please Disregard When: Where: Organizer: Aeva aevander@... Description: |
|
|
|
More Meetings (move to Zoom)
Aeva
Hi all,
As we move to having more focused meetings, I proposed to the CGC yesterday that meetings begin to move from their current locations to a community-managed Zoom location, with a published schedule. This plan was agreed to. I've received requests for, and been included in, five different topical meetings so far. After soliciting input from the interest-groups represented in each meeting, we have an initial schedule. Everyone has done their best to meet the needs of each group with respect to meeting times, though I know that these meeting times may not be perfect for everyone. I am working right now with our groups.io account to see if I can create these in a group calendar for ease of access. I also want to draw attention to a change in one existing meeting: the Triage meeting will be moving from Tuesday to Monday, so that it can better align work on Issues and PRs for the week. I'll send a follow up email on Monday morning to remind everyone about this change. Thanks for your patience while we bootstrap this process. -Aeva |
|
|
|
Event: Test Event - Please Disregard - Monday, 6 April 2020
#cal-invite
oesdk@lists.confidentialcomputing.io Calendar <oesdk@...>
Test Event - Please Disregard When: Organizer: Aeva Description: |
|
|
|
Event: OE SDK Triage Meeting
#cal-invite
oesdk@lists.confidentialcomputing.io Calendar <oesdk@...>
OE SDK Triage Meeting When: Where: Organizer: Aeva aevander@... Description: Open Enclave SDK Weekly Triage Meeting Meeting ID: 695 392 715 |
|
|
|
Cancelled Event: Test Event - Please Disregard - Monday, 6 April 2020
#cal-cancelled
oesdk@lists.confidentialcomputing.io Calendar <oesdk@...>
Cancelled: Test Event - Please Disregard This event has been cancelled. When: Organizer: Aeva Description: |
|
|
|
Event: OE SDK SIG-Architecture Meeting
#cal-invite
oesdk@lists.confidentialcomputing.io Calendar <oesdk@...>
OE SDK SIG-Architecture Meeting When: Where: Organizer: Aeva aevander@... Description: Join Zoom Meeting Meeting ID: 442 805 832 |
|
|
|
Event: OE SDK SIG-Testing Meeting
#cal-invite
oesdk@lists.confidentialcomputing.io Calendar <oesdk@...>
OE SDK SIG-Testing Meeting When: Where: Organizer: Aeva aevander@... Description: A meeting to discuss all things testing! Meeting ID: 119 965 269 |
|
|
|
Re: More Meetings (move to Zoom)
Aeva
I've created an initial set of meetings on our shared calendar - https://lists.confidentialcomputing.io/g/oesdk/calendar
toggle quoted message
Show quoted text
It looks like groups.io does not broadcast calendar invites to the mailing list, though they show up on the web view of the discussion. If you click on the link above, you can download a .ics file for each event that you'd like to attend. Current meeting list is: - triage, Monday morning (PT) - sig-architecture, Tuesday morning (PT) (*) - sig-testing, Tuesday evening (PT) (*) - CGC private meeting After a little more discussion, the fifth meeting doesn't seem necessary yet. If folks want to host additional meetings and would like any help creating the calendar entry or moderating the meeting, you're welcome to reach out to me. The TAC approved my request for an official Zoom account for the project. The account is yet to be created though, so the Zoom links may change when these meetings transition to that account. I'll update the list at that time. Once again, I want to thank everyone for their patience while this process starts up. Cheers, -Aeva (*) I've proposed the use of the term "SIG" for "Special Interest Group" in my governance patch here - https://github.com/openenclave/openenclave/pull/2778 -----Original Message-----
From: oesdk@... <oesdk@...> On Behalf Of Aeva via lists.confidentialcomputing.io Sent: Thursday, April 2, 2020 11:42 AM To: oesdk@... Subject: [oesdk] More Meetings (move to Zoom) Hi all, As we move to having more focused meetings, I proposed to the CGC yesterday that meetings begin to move from their current locations to a community-managed Zoom location, with a published schedule. This plan was agreed to. I've received requests for, and been included in, five different topical meetings so far. After soliciting input from the interest-groups represented in each meeting, we have an initial schedule. Everyone has done their best to meet the needs of each group with respect to meeting times, though I know that these meeting times may not be perfect for everyone. I am working right now with our groups.io account to see if I can create these in a group calendar for ease of access. I also want to draw attention to a change in one existing meeting: the Triage meeting will be moving from Tuesday to Monday, so that it can better align work on Issues and PRs for the week. I'll send a follow up email on Monday morning to remind everyone about this change. Thanks for your patience while we bootstrap this process. -Aeva |
|
|
|
Change code signer from Microsoft to be vendor-neutral (issue #2780)
Dave Thaler
Kicking off discussion https://github.com/openenclave/openenclave/issues/2780 ...
Currently the VS Extension and the VS Code Extension are both signed by Microsoft and hence show up in the marketplace as Publisher:Microsoft as seen on the right side of: https://marketplace.visualstudio.com/items?itemName=ms-iot.msiot-vscode-openenclave https://marketplace.visualstudio.com/items?itemName=MS-TCPS.OpenEnclaveSDK-VSIX Now that this is a CCC project not a Microsoft project, I believe these entries should be deprecated now and replaced by entries with a vendor-neutral publisher, being the Open Enclave org. (It's not feasible to change the publisher of an existing VS marketplace entry, you have to create a new entry.) There’s no specific deadline for doing this, as we can continue to use Microsoft signing in the meantime, but I believe we should move to a non-Microsoft key when one is available. Since we have to create a new entry, there’s some friction to users if we deprecate an old package and tell them to install a new package instead, so I think this ought to be done before declaring v1.0. Nuget packages on the other hand work differently. As seen at https://www.nuget.org/packages/open-enclave/ the OE SDK nuget package shows a set of individual owners, and the list CAN change without creating a new entry, as explained at https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package#managing-package-owners-on-nugetorg Nuget packets get signed with the nuget.org key, and so nuget can accept unsigned packages from any authorized package owner. Thus, an OE signing key is not needed for nuget packages. All that is required is that OE maintain the set of authorized owners of the package. So, two questions: 1) How do we get a signing usable with binary distribution mechanisms that require signed binaries to be submitted, such as VS Marketplace. 2) Is our existing process for nuget sufficient for now, of making the authorized owners of the nuget package be release managers (or individual members of the Release SIG)? Do we have adequate protections if two individuals simultaneously disappear? Do we need some group account that can be shared somehow? I think these are all questions for the Release SIG to answer, who are probably much more knowledgeable than I am on this topic, but I wanted to introduce the questions here per Aeva’s request during the triage meeting. Dave |
|
|
|
OpenEnclave SDK Samples have Issues with Latest Intel SGX SW Updates
Radhika Jandhyala
Hi,
There is an issue with running the OpenEnclave SDK 0.8.2 along with the latest Intel SGX SW updates released last night. When the latest Intel SGX Linux 2.9.1 and Intel DCAP 1.6.100.2 are installed, and the remote_attestation sample and the attested_tls sample are built with clang, these samples segfault or fail. When built using gcc, the samples work fine. We are trying to root cause and fix these issues. In the meantime, if you have an application built on OpenEnclave SDK, we recommend holding off on upgrading to the latest Intel SGX SW updates. Thanks, Radhika |
|
|
|
Re: OpenEnclave SDK Samples have Issues with Latest Intel SGX SW Updates
Radhika Jandhyala
Hi,
The problem has been identified. It only affects developers using package config and make. Please see the following issue for the workaround: https://github.com/openenclave/openenclave/issues/2828 Thanks, Radhika From: Radhika Jandhyala Sent: Thursday, April 9, 2020 1:11 PM To: oesdk@... Subject: OpenEnclave SDK Samples have Issues with Latest Intel SGX SW Updates Hi, There is an issue with running the OpenEnclave SDK 0.8.2 along with the latest Intel SGX SW updates released last night. When the latest Intel SGX Linux 2.9.1 and Intel DCAP 1.6.100.2 are installed, and the remote_attestation sample and the attested_tls sample are built with clang, these samples segfault or fail. When built using gcc, the samples work fine. We are trying to root cause and fix these issues. In the meantime, if you have an application built on OpenEnclave SDK, we recommend holding off on upgrading to the latest Intel SGX SW updates. Thanks, Radhika |
|
|
|
helloworld build error
Zhao, Xiaonan <xiaonan.zhao@...>
Hi, dear all,
Test environment: SGX PSW: Intel(R)_SGX_Windows_x64_PSW_2.7.100.2.exe, SGX SDK: open-enclave.0.8.2.nupkg, installed path: C:\openenclave cmake version 3.16.19112601-MSVC_2
When build helloworld project, met following errors, how to solve it?
******************************************************************************************
CMake Error at CMakeLists.txt:15 (find_package): Could not find a configuration file for package "OpenEnclave" that is compatible with requested version "".
The following configuration files were considered but not accepted:
C:/openenclave/lib/openenclave/cmake/openenclave-config.cmake, version: 0.8.2 (64bit)
-- Configuring incomplete, errors occurred! See also "C:/openenclave/share/openenclave/samples/helloworld/build/CMakeFiles/CMakeOutput.log".
******************************************************************************************
Thank you, Xiaonan
|
|
|
|
Re: helloworld build error
Ming-Wei Shih
This is likely due to the environment variable is not set. Can you follow the instruction here: https://github.com/openenclave/openenclave/blob/master/docs/GettingStartedDocs/Windows_using_oe_sdk.md#configure-environment-variables-for-open-enclave-sdk-for-windows?
Thanks, Ming-Wei From: oesdk@... <oesdk@...> On Behalf Of Zhao, Xiaonan via lists.confidentialcomputing.io Sent: Friday, April 10, 2020 12:24 AM To: oesdk@... Subject: [EXTERNAL] [oesdk] helloworld build error Hi, dear all, Test environment: SGX PSW: Intel(R)_SGX_Windows_x64_PSW_2.7.100.2.exe, SGX SDK: open-enclave.0.8.2.nupkg, installed path: C:\openenclave cmake version 3.16.19112601-MSVC_2 When build helloworld project, met following errors, how to solve it? ****************************************************************************************** CMake Error at CMakeLists.txt:15 (find_package): Could not find a configuration file for package "OpenEnclave" that is compatible with requested version "". The following configuration files were considered but not accepted: C:/openenclave/lib/openenclave/cmake/openenclave-config.cmake, version: 0.8.2 (64bit) -- Configuring incomplete, errors occurred! See also "C:/openenclave/share/openenclave/samples/helloworld/build/CMakeFiles/CMakeOutput.log". ****************************************************************************************** Thank you, Xiaonan |
|
|
|
Re: helloworld build error
Jordan Hand <Jordan.Hand@...>
Hi Xiaonon,
If you are still experiencing this problem would you be able to open an issue on our github repository: https://github.com/openenclave/openenclave/issues This will help us better triage the issue and help you solve it. Thanks! Jordan ________________________________ From: oesdk@... <oesdk@...> on behalf of Zhao, Xiaonan via lists.confidentialcomputing.io <xiaonan.zhao=intel.com@...> Sent: Friday, April 10, 2020 12:24 AM To: oesdk@... <oesdk@...> Subject: [EXTERNAL] [oesdk] helloworld build error Hi, dear all, Test environment: SGX PSW: Intel(R)_SGX_Windows_x64_PSW_2.7.100.2.exe, SGX SDK: open-enclave.0.8.2.nupkg, installed path: C:\openenclave cmake version 3.16.19112601-MSVC_2 When build helloworld project, met following errors, how to solve it? ****************************************************************************************** CMake Error at CMakeLists.txt:15 (find_package): Could not find a configuration file for package "OpenEnclave" that is compatible with requested version "". The following configuration files were considered but not accepted: C:/openenclave/lib/openenclave/cmake/openenclave-config.cmake, version: 0.8.2 (64bit) -- Configuring incomplete, errors occurred! See also "C:/openenclave/share/openenclave/samples/helloworld/build/CMakeFiles/CMakeOutput.log". ****************************************************************************************** Thank you, Xiaonan |
|
|