Re: [apache/incubator-teaclave-sgx-sdk] 请更新下SDK中远程认证(ue-ra)中的代码 (Issue #383)

[xin201501]

Closed #383.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/383#event-6569913432
You are receiving this because you are subscribed to this thread.

Message ID: 

Re: [apache/incubator-teaclave-sgx-sdk] 请更新下SDK中远程认证(ue-ra)中的代码 (Issue #383)

[Mingshen Sun]

Teaclave 是基于 version 4 实现的 IAS attestation 
(https://github.com/apache/incubator-teaclave/blob/master/attestation/src/service.rs#L42)
 ，可以参考对应的代码。

对于 samplecode 的更新，欢迎提交 PR 贡献。

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/383#issuecomment-1120527591
You are receiving this because you are subscribed to this thread.

Message ID: 

[apache/incubator-teaclave-sgx-sdk] 请更新下SDK中远程认证(ue-ra)中的代码 (Issue #383)

[xin201501]

我收到intel邮件提示
>2022年8月16日`DEV Intel® Software Guard Extensions Attestation Service (IAS) API 
>version 3`会结束支持，请尽快升级到version4。

我看到API v4中有些数据结构的定义似乎发生了变化。可以更新下Teaclave SGX 
SDK中`samplecode`中`ue-ra`的代码并给一些从V3迁移到V4的建议吗，谢谢。

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/383
You are receiving this because you are subscribed to this thread.

Message ID: 

Re: [apache/incubator-teaclave] 请更新下SDK中远程认证(ue-ra)的代码 (Issue #648)

[Mingshen Sun]

你好，关于 Teaclave SGX SDK 的相关问题在相应的 repo 的 issue 中提出，便于 community 进行管理，多谢。

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/648#issuecomment-1120524237
You are receiving this because you are subscribed to this thread.

Message ID: 

Re: [apache/incubator-teaclave] 请更新下SDK中远程认证(ue-ra)的代码 (Issue #648)

[Mingshen Sun]

Closed #648.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/648#event-6569321353
You are receiving this because you are subscribed to this thread.

Message ID: 

[apache/incubator-teaclave] 请更新下SDK中远程认证(ue-ra)的代码 (Issue #648)

[xin201501]

我收到intel邮件提示
>2022年8月16日`DEV Intel® Software Guard Extensions Attestation Service (IAS) API 
>version 3`会结束支持，请尽快升级到version4。

我看到API v4中有些数据结构的定义似乎发生了变化。可以更新下SDK中`samplecode`中`ue-ra`的代码并给一些从V3迁移到V4的建议吗，谢谢。

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/648
You are receiving this because you are subscribed to this thread.

Message ID: 

Re: [apache/incubator-teaclave] Renaming the dafault branch (Issue #647)

[Mingshen Sun]

Yes, to do this, we need the help of the INFRA team. Specifically, we can 
submit an issue to the INFRA team [1].

- https://issues.apache.org/jira/projects/INFRA/issues

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/647#issuecomment-1120519901
You are receiving this because you are subscribed to this thread.

Message ID: 

Re: Podling Teaclave Report Reminder - May 2022

[Mingshen Sun]

Dear Teaclave community,

Sorry for the late reply.

I'm done with the report and submitted to the wiki. [1]

Mingshen

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/May2022



## Teaclave

### Three most important unfinished issues to address before graduating:

  - Improve project structure and documentation
  - Grow the community (attracting more committers, contributors, users)
  - Publish Apache releases (resolving logistics on Apache release)

### Are there any issues that the IPMC or ASF Board need to be aware of?

None.

### How has the community developed since the last report?

Since the last report, we have organized three monthly virtual
meetups. For each meetup, we have write-ups published on the Teaclave
blog.
  - Teaclave Meetup #10:

  - Teaclave Meetup #11:

  - Teaclave Meetup #12:


We also released two versions of the Teaclave platform and Teaclave
TrustZone seperately:
  - Teaclave 0.4.0:

  - Teaclave TrustZone SDK 0.2.0:


### How has the project developed since the last report?

Here are the summaries of recent progress:

Teaclave Faas Platform:
  - Merged PRs:


Teaclave TrustZone SDK
  - Merged PRs:


Teaclave SGX SDK
  - Merged PRs:


Website

  - [blog] Teaclave Meetup #10:

  - [blog] Teaclave Meetup #11:

  - [blog] Teaclave Meetup #12:

  - [blog] Announcing Apache Teaclave (incubating) 0.4.0:

  - [blog] Announcing Apache Teaclave TrustZone SDK (incubating)
0.2.0: 


### How would you assess the podling's maturity?

  - [ ] Initial setup
  - [ ] Working towards first release
  - [x] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2021-04-18: Apache Teaclave (incubating) TrustZone SDK 0.2.0

### When were the last committers or PPMC members elected?

  - 2022-04-26: Qinkun Bao (Apache ID: qinkun), Committer

### Have your mentors been helpful and responsive?

Yes, our mentors work responsively to help us with electing new
mentors, developing new features, fixing bugs, and expanding the
community.

### Is the PPMC managing the podling's brand / trademarks?

We don't find any 3rd parties incorrectly using the podling's name and
brand.  The VP, Brand has approved the project name.
(PODLINGNAMESEARCH-175)

On Sun, May 8, 2022 at 12:58 PM Felix Cheung  wrote:
>
> Reminder
> 
> From: johndam...@apache.org 
> Sent: Wednesday, April 27, 2022 5:50:12 PM
> To: d...@teaclave.incubator.apache.org 
> Subject: Podling Teaclave Report Reminder - May 2022
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 18 May 2022.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, May 04).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might 

Re: Podling Teaclave Report Reminder - May 2022

[Felix Cheung]

Reminder

From: johndam...@apache.org 
Sent: Wednesday, April 27, 2022 5:50:12 PM
To: d...@teaclave.incubator.apache.org 
Subject: Podling Teaclave Report Reminder - May 2022

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 May 2022.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, May 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/May2022

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org
For additional commands, e-mail: dev-h...@teaclave.apache.org