Re: [VOTE] Change the default branch to "no-std" for Teaclave TrustZone SDK

+1 approve Thanks! On Wed, May 8, 2024 at 8:51 PM Yuan Zhuang wrote: > Hi community, > > I'm initiating a vote thread to propose a change in the default > branch for Teaclave TrustZone SDK > > from "master" to "no-std". > > Teaclave

Re: Podling Teaclave Report Reminder - July 2023

He, can you work on the report? Thanks! Mingshen On Wed, Jun 21, 2023 at 5:49 AM wrote: > > 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. > >

Re: [VOTE] Release Apache Teaclave (incubating) v0.6.0-rc.1

+1 approve. I have tested the building. Mingshen On Mon, Jun 12, 2023 at 5:26 AM He Sun wrote: > Hi all, > > I am pleased to be calling this vote for the release of > Apache Teaclave (incubating) 0.6.0 (release candidate 1). > > The release candidate to be voted over is available at: > -

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

+1 approve On Tue, May 9, 2023 at 1:17 AM He Sun wrote: > Hi all, > > I am pleased to be calling this vote for the release of > Apache Teaclave (incubating) 0.5.1 (release candidate 1). > > The release candidate to be voted over is available at: > -

Re: Podling Teaclave Report Reminder - April 2023

Hi He and Ran, Can you work together on the April report? Thanks! Mingshen On Fri, Apr 7, 2023 at 2:55 AM wrote: > 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

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

+1 Thanks. Mingshen On Sun, Mar 26, 2023 at 7:33 PM He Sun wrote: > > Hi all, > > I am pleased to be calling this vote for the fifth release of > Apache Teaclave (incubating) 0.5.0 (release candidate 1). > > The release candidate to be voted over is available at: > -

GSoC 2023 proposals

Dear Teaclave community, Apache Teaclae (incubating) is participating in GSoC 2023. We are in the phase of submitting proposals. Please let me know if you are interested in GSoC and want to contribute to Teaclave. I'm more than happy to mentor you through the summer. Thanks! Here are some

Re: [apache/incubator-teaclave] Task logger (PR #676)

The original design is to separate executors with other components to make it more flexible. In this implementation, if I understand correctly, executors are talking to the storage directly. Why not return the logs with the function return value instead? -- Reply to this email directly or

Fwd: [ACTION REQUIRED] Time to create GSoC ideas

Hi all, It’s time to propose GSoC 2023 ideas. Please contact me if you want to join and brainstorm ideas. Thanks! Mingshen -- Forwarded message - From: Sanyam Goel Date: Wed, Feb 8, 2023 at 9:47 AM Subject: [ACTION REQUIRED] Time to create GSoC ideas To: , Maxim Solodovnik ,

Re: [apache/incubator-teaclave] [docs] Fix typo (PR #675)

Merged #675 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/675#event-8463858682 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Access control service (Issue #674)

Yes, ACS is designed to be the service to evaluate the access control policy. Using a dedicated service makes the policy evaluation more flexible. However, we didn't have time to integrate with the current ACS. In the current implementation, access control policy is hard coded in the

Re: [VOTE] Graduate Apache Teaclave (incubating) to a Top Level Project

Hi Gordon, I'm glad to hear that Teaclave is considered for graduation. I fully support the proposal. (Carrying my +1 vote from private@teaclave) Though I'm not familiar with the graduation process, I do see several gaps for graduation. For example: - License/Copyright reviews and compliance

Re: [apache/incubator-teaclave] readme: add a needed break (PR #671)

Merged #671 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/671#event-8217511105 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] CI pipeline issue: Code scanning / Analyze cpp (pull_request) (Issue #673)

Closed #673 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/673#event-8217512609 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] readme: missing words (PR #672)

Merged #672 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/672#event-8217511782 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Improve function comment layout for pdoc (PR #670)

Merged #670 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/670#event-8217509614 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Upgrade to Rust SGX SDK 2.0.0 (PR #666)

Merged #666 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/666#event-8217506288 You are receiving this because you are subscribed to this thread. Message ID:

Re: [VOTE] Release Apache Teaclave (incubating) Java TEE SDK v0.1.0-rc.1

Hi Shaojun, I check the followings: - Are release files in correct location? Yes - Do release files have the word incubating in their name? Yes - Are the digital signature and hashes correct? Yes - Does DISCLAIMER file exist? Yes - Do LICENSE and NOTICE files exists? YES - Is the LICENSE and

[apache/incubator-teaclave] CI pipeline issue: Code scanning / Analyze cpp (pull_request) (Issue #673)

There is CI pipeline issue: Code scanning / Analyze cpp (pull_request) -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/673 You are receiving this because you are subscribed to this thread. Message ID:

Re: [VOTE] Release Apache Teaclave (incubating) Java TEE SDK v0.1.0-rc.1

Hi Shaojun, I check the followings: - Are release files in correct location? Yes - Do release files have the word incubating in their name? Yes - Are the digital signature and hashes correct? Yes - Does DISCLAIMER file exist? Yes - Do LICENSE and NOTICE files exists? NO - Is the LICENSE and

Welcoming He Sun (@hsun) as Teaclave committer

is working on upgrading to Teaclave SGX SDK 2.0. Here are the contributions from him: https://github.com/apache/incubator-teaclave/commits?author=henrysun007 Congratulations to He and thanks! Mingshen Sun Apache Teaclave (incubating) PPMC https://mssun.me

Re: [apache/incubator-teaclave] Support persistent data storage (#321)

Closed #321 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/321#event-8118693355 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Support persistent data storage (#321)

Yes. This issue can be closed. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/321#issuecomment-1366343030 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Upgrade to Rust SGX SDK 2.0.0 (PR #666)

> @mssun I cannot open PR to > https://github.com/apache/incubator-teaclave-crates as it is empty. So I > pushed the crates to https://github.com/mesatee/crates. The code is tested. > You can upload the code directly to `incubator-teaclave-crates`. Let me know > after the upload. I created a

Fwd: New GitBox/GitHub repository set up: incubator-teaclave-crates.git

Hi all, As discussed in the contributor meetup, I created a repo for hosting our customized third-party crates for SGX SDK. Mingshen -- Forwarded message - From: GitBox Date: Wed, Dec 21, 2022 at 9:20 PM Subject: New GitBox/GitHub repository set up:

Re: Teaclave Contributor Meetup (Bi-weekly)

I just changed the meeting schedule to weekly. Let's meet next week with the same link. Thanks. Teams: https://teams.live.com/meet/9361052105209 Notes: https://mssun.notion.site/Teaclave-Contributor-Meetup-38ad92d951a24de187f1a9d1bab8c5dc Mingshen On Wed, Dec 14, 2022 at 8:07 PM Mingshen Sun

Re: Teaclave Contributor Meetup (Bi-weekly)

at 11:28 PM Shaojun Wang wrote: > > I will attend on time. > > Shaojun Wang > > > 2022年12月6日 13:42，Mingshen Sun 写道： > > > > Hi all, > > > > The current contributors spread in different companies and we need a > > channel to sync the curre

Teaclave Contributor Meetup (Bi-weekly)

Hi all, The current contributors spread in different companies and we need a channel to sync the current status and discuss the roadmap, architecture and development issues. Therefore, I suggest starting a bi-weekly meetings among all contributors for discussion. The first meeting will be next

Re: [VOTE] Release Apache Teaclave (incubating) Java TEE SDK v0.1.0-rc.1

Hi Shaojun, I check the followings: - Are release files in correct location? Yes - Do release files have the word incubating in their name? Yes - Are the digital signature and hashes correct? Yes - Does DISCLAIMER file exist? No - Do LICENSE and NOTICE files exists? No - Is the LICENSE and

Re: Teaclave Java TEE SDK First Release

Hi Shaojun, Yes, we also need a good document and render in the Teaclave homepage: https://teaclave.apache.org/. The website repo is: https://github.com/apache/incubator-teaclave-website mingshen On Fri, Nov 18, 2022 at 8:04 PM Mingshen Sun wrote: > > Hi Shaojun, > > We shou

Re: Teaclave Java TEE SDK First Release

Hi Shaojun, We should also have a complete license check and list all third-party licenses properly. For example: - https://github.com/apache/incubator-teaclave/tree/master/licenses - https://github.com/apache/incubator-teaclave-sgx-sdk/tree/master/licenses mingshen On Tue, Nov 15, 2022 at

Welcome Java TEE SDK to Teaclave

Dear Teaclave community, After going through different logistics during these weeks, finally, Java TEE SDK (origin name: JavaEnclave) has joined Teaclave as a sub-project. [1] Teaclave Java TEE SDK is a Java confidential computing programming framework. It follows the host-and-enclave partition

Re: [apache/incubator-teaclave] Bugfix of leveldb and rust sdk (PR #665)

Merged #665 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/665#event-7779788368 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] [SURVEY] What companies or open source projects are using the Apache Teaclave (Incubating) platform? (#310)

@ChuanDou2021 Thanks for the suggestions. The "Used by" feature is automatically generated if GitHub find public dependencies on this repo:

Re: [apache/incubator-teaclave] Update leveldb (PR #661)

Merged #661 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/661#event-7708564361 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Update leveldb (PR #661)

Yes, I still remember that Zhaofeng and I had a long discussion on this and we decided to put in the Teaclave repo. There are pros and cons. I think the most important reason is about the ownership. We want to maintain LevelDB for SGX as part of Teaclave. Definitely, this makes it not obvious

Re: [apache/incubator-teaclave-sgx-sdk] Request update for rust nightly version (Issue #386)

@clangenb Hi, there are still some missing parts to merge version 2. I would be grateful if you would help us. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/386#issuecomment-1292951815 You are receiving this because you are

Re: [apache/incubator-teaclave] Update leveldb (PR #661)

Hi @henrysun007, thanks for the PR. The reason we choose to put in the `common` directory is that we have changed `rusty_leveldb` a lot, and we don't have any plan to upstream the changes. Therefore, we'd like to keep it in the Teaclave codebase as a part of Teaclave. I saw you're using a

Re: [VOTE] Accept Teaclave Java TEE SDK to Apache Teaclave (incubating)

Thanks to everyone that participated. The vote to accept JavaEncalve (will be Teaclave Java TEE SDK under Teaclave) to Apache Teaclave (incubating) is now closed. The vote PASSED with 3 binding +1, 3 non binding +1 and 0 -1 votes: Binding votes: - Yu Ding (PPMC) - Ran Duan (PPMC) - Mingshen Sun

Re: [VOTE] Accept Teaclave Java TEE SDK to Apache Teaclave (incubating)

+1 Agree. Thanks, Shaojun. On Thu, Oct 20, 2022 at 12:43 AM Ran Duan wrote: > > +1 Agree > > I've been discussing the donation of the project with Shaojun recently. I > think JavaEnclave is aligned with Teaclave's security design goals and > extends the important Java runtime to Teaclave. > >

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.6.0 in /examples/rust/builtin_echo (PR #659)

Merged #659 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/659#event-7617702334 You are receiving this because you are subscribed to this thread. Message ID:

Re: [VOTE] Accept Teaclave Java TEE SDK to Apache Teaclave (incubating)

they are recognized and noted, then they can be addressed during > incubation. > > #### Project Name > > Teaclave Java TEE SDK was initially developed and applied within Alibaba Cloud > as a closed-source project which was called JavaEnclave. > > Inexperience with Open Source: &

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.6.0 in /examples/rust/builtin_echo (PR #659)

@dependabot rebase? -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/659#issuecomment-1281824533 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Ignore license check for txt files (PR #660)

Merged #660 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/660#event-7607816642 You are receiving this because you are subscribed to this thread. Message ID:

[apache/incubator-teaclave] Ignore license check for txt files (PR #660)

## Description Ignore license check for txt files. You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave/pull/660 -- Commit Summary -- * Ignore license check for txt files -- File Changes -- M .licenserc.yaml (1) -- Patch Links

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.5.6 in /examples/rust/builtin_echo (PR #650)

@dependabot rebase? -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/650#issuecomment-1281760961 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Improve CI (PR #658)

Merged #658 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/658#event-7607399297 You are receiving this because you are subscribed to this thread. Message ID:

Welcome Yuan Zhuang as Teaclave PPMC

Dear Teaclave community, Let's welcome Yuan Zhuang as our new Teaclave PPMC member. Yuan started working on Teaclave TrustZone SDK one year ago and made several major contributions on the project. She also led the second release of Teaclave TrustZone SDK. Mingshen

Welcome Ran Duan as Teaclave PPMC

Dear Teaclave community, Let's welcome Ran Duan as our new Teaclave PPMC member. Ran has contributed a lot to the Teaclave SGX SDK repository for years. Right now, he is working on our next release. His commits can be seen at:

Re: Podling Teaclave Report Reminder - July 2022

Dear Teaclave community, Unfortunately, due to my time conflicts, we failed to submit the July report. We should prepare for the August podling report. Mingshen On Wed, Jun 29, 2022 at 8:04 PM Mingshen Sun wrote: > > Thanks for the reminder. > > @rd...@apache.org Can you work on

A tutorial to learn how to build secure applications for Intel SGX platforms in C and Rust

Dear Teaclave community, I'd like to share a tutorial on SGX and using Teaclave SGX SDK to develop SGX enclaves. Link: https://github.com/plaublin/intel_sgx_tutorial#teaclave-sgx-sdk-rust Mingshen - To unsubscribe, e-mail:

Re: Podling Teaclave Report Reminder - July 2022

Thanks for the reminder. @rd...@apache.org Can you work on this report this time? I think there are more updates in the Teaclave SGX SDK. You can see my previous writeups in the blog: https://teaclave.apache.org/blog/ Once the report is updated to the wiki, I'll push it to the blog also.

Teaclave Meetup #13

. Thanks. Also, the old zoom link should be invalid. Let use my Zoom link for this time: Mingshen Sun is inviting you to a scheduled Zoom meeting. Topic: Mingshen Sun's Personal Meeting Room Join Zoom Meeting https://zoom.us/j/7311634518?pwd=emVSU3E1ejVUQUVkazc0NFVjbVUrZz09 Meeting ID: 731 163 4518

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.5.6 in /examples/rust/builtin_echo (PR #650)

The (fast) build depends on the mesapy binary which is hosted by the third party (which is currently not available): https://github.com/apache/incubator-teaclave/runs/7085415421?check_suite_focus=true#step:6:223 We should solve this first, move the mesapy binary to the apache INFRA. E.g.,

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.5.6 in /examples/rust/builtin_echo (PR #650)

Re-running CI to make sure all tests passed. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/650#issuecomment-1168174005 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.5.6 in /examples/rust/builtin_ordered_set_intersect (PR #651)

Re-running CI to make sure all tests passed. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/651#issuecomment-1168174142 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Bump prost-types from 0.6.1 to 0.8.0 in /services/proto/proto_gen (PR #649)

Teaclave's dependencies are pinned to specific versions and vendored here: https://github.com/apache/incubator-teaclave/tree/master/third_party. We don't upgrade crates versions like this. -- Reply to this email directly or view it on GitHub:

Re: [apache/incubator-teaclave] Bump prost-types from 0.6.1 to 0.8.0 in /services/proto/proto_gen (PR #649)

Closed #649. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/649#event-6890225912 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.5.6 in /config/config_gen (PR #652)

Closed #652. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/652#event-6890219418 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.5.6 in /sdk/rust (PR #653)

Closed #653. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/653#event-6890218821 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.5.6 in /config/config_gen (PR #652)

Teaclave's dependencies are pinned to specific versions and vendored here: https://github.com/apache/incubator-teaclave/tree/master/third_party. We don't upgrade crates versions like this. -- Reply to this email directly or view it on GitHub:

Re: [apache/incubator-teaclave] Bump regex from 1.5.4 to 1.5.6 in /sdk/rust (PR #653)

Teaclave's dependencies are pinned to specific versions and vendored here: https://github.com/apache/incubator-teaclave/tree/master/third_party. We don't upgrade crates versions like this. -- Reply to this email directly or view it on GitHub:

No Community Meetup in May

Hi all, Sorry for the late notice. There’s no meetup today. Let’s meet next month! Mingshen

Re: Places of storing pre-built assets for CI cache on Apache infra

lies.apache.org/authoring.html for instructions how to > push things there. There are also instructions how to do this from Jenkins, > Buildbot and Github Actions. > > Martin > > On Tue, May 10, 2022 at 6:19 AM Mingshen Sun wrote: > > > Hi community, > > > > W

Places of storing pre-built assets for CI cache on Apache infra

Hi community, We are facing an issue of storing some pre-built assets for CI usage. >From what I understand, there are two places for hosting these files: - SVN: https://dist.apache.org/repos/dist/dev/incubator/teaclave/assets/xxx.tar.gz (I don't think this is a proper place. Because,

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

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:

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

你好，关于 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)

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:

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

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:

Re: Podling Teaclave Report Reminder - May 2022

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

Re: Podling Teaclave Report Reminder - May 2022

Hi Furkan, Sorry, I overlooked this email. I’ll prepare the report tomorrow. Thanks! Mingshen On Tue, May 3, 2022 at 4:15 PM Furkan KAMACI wrote: > Hi, > > Is there anybody working on the report? Feel free to ask if you need help. > > Kind Regards, > Furkan KAMACI >

Welcoming Qinkun Bao (@qinkun) as Teaclave committer

frameworks. Congratulations to Qinkun and thanks! Mingshen Sun Apache Teaclave (incubating) PPMC https://mssun.me [1] https://github.com/apache/incubator-teaclave/commits?author=qinkunbao [2] https://p4cleanroom.com

Re: [apache/incubator-teaclave-sgx-sdk] performance overhead (Issue #379)

Hi, can you also put the code, testbed, and how you measure the overhead? This will be very helpful when discussing the performance overhead. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/379#issuecomment-1110311892 You are

Re: [apache/incubator-teaclave-sgx-sdk] [SURVEY] What companies or open source projects are using Apache Teaclave (Incubating) SGX SDK? (#239)

Thanks, this is very helpful! > We are using it in blockchain. We think SGX will be the infrastructure for > web3.0 -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/239#issuecomment-1107417395 You are receiving this because you

Re: May 2022 Podling Reporting Timeline

Hi all, I'm from the Teaclave project. I just noticed that we missed April's report because of the reminder issue. Should we add it in May's report also? I see some discussions here but no conclusion yet. For Teaclave, we have no problem with adding an additional report in May. Mingshen On

Re: [apache/incubator-teaclave] Update copyright year to 2022 (PR #646)

Merged #646 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/646#event-6451144231 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] Fix release guide (PR #645)

Merged #645 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/645#event-6451135873 You are receiving this because you are subscribed to this thread. Message ID:

[apache/incubator-teaclave] Update copyright year to 2022 (PR #646)

## Description Update copyright year to 2022. You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave/pull/646 -- Commit Summary -- * Update copyright year to 2022 -- File Changes -- M NOTICE (2) -- Patch Links --

[apache/incubator-teaclave] Fix release guide (PR #645)

## Description Fix some minor issues in the release guide document. You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave/pull/645 -- Commit Summary -- * Fix release guide -- File Changes -- M docs/release-guide.md (3) -- Patch

Re: [apache/incubator-teaclave] Update run-teaclave-services.sh (PR #643)

Merged #643 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/643#event-6450461829 You are receiving this because you are subscribed to this thread. Message ID:

[ANNOUNCE] Apache Teaclave (incubating) 0.4.0 released

apache/incubator-teaclave/releases/tag/v0.4.0 A link to the download can be found here: https://teaclave.apache.org/download/ To learn more about Teaclave, please visit: https://teaclave.apache.org/ Best, Mingshen Sun The Apache Teaclave (incubating) Team === *Disclaimer* Apache Teaclave (incu

[apache/incubator-teaclave] Release 0.4.0 (PR #644)

## Description The vote of releasing 0.4.0 in general@incubator has passed [1]. Please approve to merge into the master branch. Thanks. [1] https://lists.apache.org/thread/tjvpcqrmhnb76r8pr34gn1djrwdr7kf9 You can view, comment on, or merge this pull request online at:

Re: [apache/incubator-teaclave] Update run-teaclave-services.sh (PR #643)

Since we are in the process of releasing v0.4.0. This PR will be merged later. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/643#issuecomment-1083992634 You are receiving this because you are subscribed to this thread. Message ID:

Re: [Scheduled] Teaclave Meetup #11

, Mar 16, 2022 at 7:23 PM Mingshen Sun wrote: > > Dear Teaclave Community, > > We are going to have the 11th monthly Teaclave (virtual) meetup. This > is the second meetup in 2022. > > - 19:00-20:00 on Thursday, March 31, 2022 (PT) > > You can find the corresponding date

Re: [apache/incubator-teaclave] 我想问一个很初级的问题。。。。 (Issue #642)

你好，应用程序（app）和安全区（enclave）的结构。 -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/642#issuecomment-1081019282 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/incubator-teaclave] 我想问一个很初级的问题。。。。 (Issue #642)

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

[RESULT] [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

* Hongbo Chen (binding) * Yulong Zhang (binding) * Ran Duan (binding) * Yu Ding (binding) * Tongxin Li (binding) * Rundong Zhou (binding) * Qinkun Bao * Yingchun Gao 0 votes * No votes -1 votes * No votes Vote thread: https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk Best, Mingshen Sun

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

(binding) * Rundong Zhou (binding) * Qinkun Bao * Yingchun Gao 0 votes * No votes -1 votes * No votes Best, Mingshen Sun On Fri, Mar 25, 2022 at 1:20 PM Rundong Zhou wrote: > > +1 > > Rundong > > On 2022/03/22 06:58:17 Mingshen Sun wrote: > > Hi all, > > > >

Re: [apache/incubator-teaclave] [SGx Mode] Bugs in Teaclave deployment on azure (Issue #640)

@hiteshvpatel256, this could be an issue of detecting sgx devices on Azure in the `run-teaclave-services.sh` script. Let me setup a new one on Azure and go through the instruction to see the root cause again. -- Reply to this email directly or view it on GitHub:

Re: [apache/incubator-teaclave] Failed to start teaclave service (Issue #641)

> Looks only "teaclave-execution-service exited with code 1" means failure? In this case, the exit code may not help. Seems that you are building for SGX hardware mode. For this mode, the service need to communicate with an attestation service (IAS or DCAP service depends on your setup). If

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.2

? ☑ Is the NOTICE year correct? Yes. ☑ Can you compile from source? Are the instruction clear? Yes. ☑ Are there any unexpected binary files in the release? No. Mingshen Mingshen Sun On Tue, Mar 22, 2022 at 11:02 PM Yuan Zhuang wrote: > > Hi all, > > I am pleased to be calling this vote fo

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

gt; Hi Mingshen Sun, > > Thanks for your support. > > I have one question, > > 1. I try to test this version in Macbook M1. This is not working in my mac. > Could it support Mac M1?

[VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

t just committers, please feel free to try out the release candidate and provide your votes. Please also reply with things you have checked. A checklist for reference: - https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist Best, Mings

[apache/incubator-teaclave] Pre-release v0.4.0-rc.1 - Apache Teaclave (incubating) 0.4.0 Release Candidate 1

Apache Teaclave (incubating) is an open source universal secure computing platform, making computation on privacy-sensitive data safe and simple. This is the fourth official Apache incubator release. In this release, we mainly focus on better user management, task management, performance

[apache/incubator-teaclave] Fix broken link (PR #639)

Fix broken link You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave/pull/639 -- Commit Summary -- * Fix broken link -- File Changes -- M README.md (2) -- Patch Links --

Re: [apache/incubator-teaclave] Add release guide in docs (PR #638)

Merged #638 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/638#event-6272569013 You are receiving this because you are subscribed to this thread. Message ID:

[apache/incubator-teaclave] Add release guide in docs (PR #638)

## Description Add a release guide to help releasing Apache versions in the future. ## Type of change - [x] New doc ## How has this been tested? N/A ## Checklist - [x] Fork the repo and create your branch from `master`. - [x] If youve added code that should be tested, add tests. - [x] If

Re: [apache/incubator-teaclave] Better task state error and fix cancel error issue in the example (PR #637)

Merged #637 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/637#event-6270117710 You are receiving this because you are subscribed to this thread. Message ID:

[apache/incubator-teaclave] Better task state error and fix cancel error issue in the example (PR #637)

## Description Better task state error and fix cancel error issue in the example. ## Type of change (select or add applied and delete the others) - [x] Bug fix ## How has this been tested? CI: https://ci.mesalock-linux.org/mssun/incubator-teaclave/161 ## Checklist - [x] Fork the repo and

Re: [apache/incubator-teaclave] `list_functions` and `get_function` have different access controls (Issue #624)

Closed #624 via #636. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/624#event-6267545892 You are receiving this because you are subscribed to this thread. Message ID:

  1   2   3   4   5   6   7   8   9   10   >