Re: [VOTE] Release Apache Teaclave (incubating) v0.6.0-rc.1
Hi all, +1 Approval. I checked all licenses and ran all tests locally. Everything worked as expected. Thanks. Best, Yu On Tue, Jun 13, 2023 at 11:24 PM gaoyingchun wrote: > +1 approve. I have compiled it from source, and it works as expected on > all of the tests. > > -邮件原件- > 发件人: He Sun > 发送时间: 2023年6月12日 20:26 > 收件人: dev@teaclave.apache.org > 主题: [VOTE] Release Apache Teaclave (incubating) v0.6.0-rc.1 > > 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: > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.6.0-rc.1/ > > The release candidate is signed with a GPG key > (777A1FBA5762313CD86EC2727144C76533763CD9) available at: > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS > > The Git commit for this release is: > - > https://github.com/apache/incubator-teaclave/commit/8693e5cb26d1739b7b1cb3d53a04943e39535565 > > The release note is available in: > - https://github.com/apache/incubator-teaclave/releases/tag/v0.6.0-rc.1 > > Build guide and get started instructions can be found at: > - > https://github.com/apache/incubator-teaclave/blob/v0.6.0-rc.1/docs/my-first-function.md > > The short version of building Teaclave from the source tarball: > > ``` > $ wget > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.6.0-rc.1/apache-teaclave-0.6.0-rc.1-incubating.tar.gz > $ tar zxvf apache-teaclave-0.6.0-rc.1-incubating.tar.gz && cd \ > apache-teaclave-0.6.0-rc.1-incubating > $ # Instructions to verify the source tar: > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \ -it > teaclave/teaclave-build-ubuntu-2004-sgx-2.17.1:0.2.0 \ bash -c ". > /root/.cargo/env && \ . /opt/sgxsdk/environment && \ mkdir -p build && cd > build && \ cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && > \ make -j" > ``` > > The vote will be open for at least 72 hours. Everyone is welcome to vote. > Please vote by replying to this thread explicitly. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Anyone can participate in testing and voting, not 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, > > He Sun > Apache Teaclave (incubating) > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > >
Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1
Hi team, Regarding my +1, I downloaded the source code and I can confirm that it compiles and works as expected on all of the samples. Best, Yu On Sun, May 14, 2023 at 10:11 PM Justin Mclean wrote: > HI, > > It would be helpful if people listed what they checked in the release > rather than just saying "+1". > > For instance I would normal say something along these lines: > > I checked: > - incubating in name > - signature and hashes are fine > - DISCLAIMER exists > - LICENSE and NOTICE are correct > - All ASF files have ASF headers > - No unexpected binary files > - Can compile from source > > I will not that this release still seem to include GPL software. Did > anyone check for this? > > Kind Regards, > Justin > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > >
Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1
+1 approve On Fri, May 12, 2023 at 7:43 AM Yuan Zhuang wrote: > +1 approve > > On 2023/05/09 08:16:19 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: > > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.5.1-rc.1/ > > > > The release candidate is signed with a GPG key available at: > > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS > > > > The Git commit for this release is: > > - > https://github.com/apache/incubator-teaclave/commit/0d95f05395b95d3efa33ebe8ab85f8175cf209ea > > > > The release note is available in: > > - https://github.com/apache/incubator-teaclave/releases/tag/v0.5.1-rc.1 > > > > Build guide and get started instructions can be found at: > > - > https://github.com/apache/incubator-teaclave/blob/v0.5.1-rc.1/docs/my-first-function.md > > > > The short version of building Teaclave from the source tarball: > > > > ``` > > $ wget > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.5.1-rc.1/apache-teaclave-0.5.1-rc.1-incubating.tar.gz > > $ tar zxvf apache-teaclave-0.5.1-rc.1-incubating.tar.gz && cd \ > > apache-teaclave-0.5.1-incubating > > $ # Instructions to verify the source tar: > > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files > > > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \ > > -it teaclave/teaclave-build-ubuntu-2004-sgx-2.17.1:0.2.0 \ > > bash -c ". /root/.cargo/env && \ > > . /opt/sgxsdk/environment && \ > > mkdir -p build && cd build && \ > > cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \ > > make -j" > > ``` > > > > The vote will be open for at least 72 hours. Everyone is welcome to > > vote. Please vote by replying to this thread explicitly. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Anyone can participate in testing and voting, not 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, > > > > He Sun > > Apache Teaclave (incubating) > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > >
Re: [VOTE] Graduate Apache Teaclave (incubating) to a Top Level Project
+1 Support. Looking forward to the graduation! On 2023/01/29 04:19:51 Gordon wrote: > Dear all in Teaclave community, > > We are starting a vote to graduate Apache Teaclave (incubating) as a Top > Level Project. > > Apache Teaclave has incubated with the Apache Incubator since August 19th, > 2019. During this period, the project has worked towards incubation with > the following milestones: > * The project has reached a stage where its name and copyright are in > bounds with the Apache Software Foundation legal processes. > * The project is able to make releases sanctioned by Apache, following > proper guidelines and following vote processes. > > In this thread, I would like to encourage that we consider moving Apache > Teaclave out of the incubator and propose a motion to the IPMC and board to > establish it as a top-level project at the ASF. Please provide your vote > accordingly: > [ ] +1 Yes, I support the Teaclave project to graduate from the Apache > Incubator. > [ ] +0 No opinion. > [ ] -1 No, the Teaclave project is not ready to graduate, because... Thank > you for participating in the vote. Please respond to the thread with your > vote and comments. > > This vote will stay open for at least 72 hours or until next Friday. > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Welcome Java TEE SDK to Teaclave
Awesome! Welcome! On Thu, Nov 10, 2022 at 21:39 Mingshen Sun wrote: > 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 programming model > defined by Intel-SGX SDK. Teaclave Java TEE SDK provides an elegant > way to divide a java project into host and enclave modules, where the > enclave module is a provider of a user-defined service interface which > is similar to the Java SPI model. Teaclave Java TEE SDK could help you > to develop and build a Java confidential computing project with high > efficiency. > > The repository of Java TEE SDK is: > https://github.com/apache/incubator-teaclave-java-tee-sdk > > Initial committers of Java TEE SDK also join Teaclave as committers > and continue contribute to the project. > > - Lei Yu (@yulei) > - Sanhong Li (@sanhongli) > - Shaojun Wang (@shaojunwang) > - Ziyi Lin (@ziyilin) > > Let's welcome our new committers to the Teaclave community. > > Best, > Mingshen > > [1] > https://teaclave.apache.org/blog/2022-10-17-accepting-java-enclave-proposal/ > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > >
Re: [VOTE] Accept Teaclave Java TEE SDK to Apache Teaclave (incubating)
+1 Agree Java is important to Teaclave. Strongly recommed. On 2022/10/18 06:01:10 汪少军 wrote: > Hi all, > > Teaclave Java TEE SDK is a Java confidential computing programming framework > which was > developed and applied in Alibaba Cloud. > > On behalf of the Teaclave Java TEE SDK project, we decide to donate it to > Apache Teaclave(incubating) > as a subproject. we using part of the incubator proposal template, but omit > some irrelevant sections. > > Proposal === > > ## Abstract > > Teaclave Java TEE SDK is a Java confidential computing programming framework. > It follows the host-and-enclave partition programming model defined by > Intel-SGX SDK. > Teaclave Java TEE SDK provides an elegant way to divide a java project into > host and > enclave modules, where the enclave module is a provider of a user-defined > service > interface which is similar to the Java SPI model. Teaclave Java TEE SDK could > help you to develop and build a Java confidential computing project with > high efficiency. > > ## Proposal > > Teaclave Java TEE SDK is a pure Java SDK for Java confidential computing. It > eases > the interactions between secured and unsecured environment with a few concise > APIs. > From user's aspect, creating an enclave environment and invoking confidential > computing services would be as simple as invoking SPI services. > > ### Background > > The Teaclave Java TEE SDK project is being actively developed within Alibaba > Cloud. > > ### Rationale > > Teaclave Java TEE SDK is a Java confidential computing programming framework. > The goal of Teaclave is to provide a universal secure computing platform for > multiple programming languages. Teaclave currently supports Rust, Python and > WebAssembly, but Java is still missing. Teaclave Java TEE SDK would be an > important piece of the puzzle. > > ### Initial Goals > > - Transfer the repository to the Apache Incubator under the Teaclave project > - Code cleanup and more documentation > > Meritocracy: > > Teaclave Java TEE SDK project was originally developed and reviewed by > Shaojun Wang/Ziyi Lin/Lei Yu/Sanhong Li within Alibaba Cloud. > We encourage everyone to ask questions and create pull requests for the > project. > > Community: > > Teaclave Java TEE SDK was developed and applied within Alibaba Cloud before > it was donated to Teaclave. > > Core Developers: > > The core developers are: > - Shaojun Wang (jeffery@alibaba-inc.com) > - Ziyi Lin (cengfeng@alibaba-inc.com) > > Alignment: > > The project is complimentary of Teaclave's TEE backends. > > ### Known Risks > > An exercise in self-knowledge. Risks don't mean that a project is > unacceptable. > If 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: > > Teaclave Java TEE SDK has been reviewed by Mingshen Sun, who is from the > Teaclave > community. He's familiar with The Apache Way for the open-source community. > > Length of Incubation: > > The project will be in incubation with Apache Teaclave (incubating) project. > > ### Documentation > > - Teaclave Java TEE SDK's documentation will be submit to Teaclave PPMC for > review > by email priv...@teaclave.apache.org > > ### Initial Source > > - Teaclave Java TEE SDK's source code will be submit to Teaclave PPMC for > review > by email priv...@teaclave.apache.org > > ### Source and Intellectual Property Submission Plan > > We will submit a Software Grant for this project later. > > External Dependencies: > > The dependencies have Apache compatible license, which is provided under the > BSD 2-Clause license and GPL2.0 license. One dependency of Teaclave Java TEE > SDK > is GraalVM SubstraceVM with GPL2.0 license, it's used as the enclave module's > native image compiler, and Teaclave Java TEE SDK has contributed some patches > to GraalVM and they had been contained in GraalVM's official releases assets. > Teaclave Java TEE SDK is dependent on GraalVM's official releases and doesn't > make any modifications to GraalVM's source code, so there's no legal risk. > https://www.apache.org/legal/resolved.html > > Cryptography: > > N/A > > ### Required Resources > > Mailing lists: > > The project shares the same mailing list of Teaclave. > > Git Repositories: > > - N/A > > Issue Tracking: > > Same with Teaclave. > > Other Resources: > > N/A > > ### Initial Committers > > - Shaojun Wang (jeffery@alibaba-inc.com) > - Ziyi Lin (cengfeng@alibaba-inc.com) > - Lei Yu (lei@alibaba-inc.com) > - Sanhong Li (sanhong@alibaba-inc.com) > > from 阿里邮箱 macOS - To unsubscribe, e-mail: dev-unsubs
Re: [apache/incubator-teaclave-sgx-sdk] Mesalock libraries heavily outdated (Issue #397)
sure. i'd like to merge! ty! -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/397#issuecomment-1168986867 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] build(deps): bump commons-io from 2.4 to 2.7 in /samplecode/mio/client-java (PR #390)
Merged #390 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/390#event-6749945172 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] build(deps): bump httpclient from 4.4 to 4.5.13 in /samplecode/mio/client-java (PR #389)
Merged #389 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/389#event-6749944464 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] build(deps): bump gson from 2.8.2 to 2.8.9 in /samplecode/ue-ra/ue-ra-client-java (PR #385)
Merged #385 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/385#event-6749943377 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] build(deps): bump gson from 2.8.2 to 2.8.9 in /samplecode/mio/client-java (PR #384)
Merged #384 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/384#event-6749942774 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Fix error typo (PR #382)
@jnigri thank you for the contribution! -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/382#issuecomment-1117594209 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Fix error typo (PR #382)
Merged #382 into v2.0.0-preview. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/382#event-6550315160 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Use simulation mode on MacOS M1 docker (Issue #378)
hey guys, M1 is not currently supported because this SDK current links to Intel SGX SDK (prebuilt by Intel, x86_64 only). also i'm trying to make the v2.0.0-preview branch compatible with M1. basically it's less coupled with upstream Intel SGX SDK so I think it might be possible ... -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/378#issuecomment-1105602159 You are receiving this because you commented. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] feat: new feature gate `initenv` to disable env ocalls on demand (PR #377)
Merged #377 into v2.0.0-preview. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/377#event-6392700297 You are receiving this because you are subscribed to this thread. Message ID:
[apache/incubator-teaclave-sgx-sdk] feat: new feature gate `initenv` to disable env ocalls on demand (PR #377)
we need a way to construct "0 ocall enclave" and this is the first move: make the env var access optional in sgx_tstd. new feature gate proposed `initenv` which is by default open (backward compatible). disable this feature could statically remove `ocall::initenv` and `ocall::initargs`. You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/377 -- Commit Summary -- * feat: new feature gate `initenv` to disable env ocalls on demand -- File Changes -- M sgx_tstd/Cargo.toml (3) M sgx_tstd/src/rt.rs (43) M sgx_tstd/src/sys/mod.rs (6) -- Patch Links -- https://github.com/apache/incubator-teaclave-sgx-sdk/pull/377.patch https://github.com/apache/incubator-teaclave-sgx-sdk/pull/377.diff -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/377 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Fix OPT_LIBS_PATH docker env (PR #376)
Merged #376 into v2.0.0-preview. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/376#event-6314861624 You are receiving this because you are subscribed to this thread. Message ID:
Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.2
+1 approve Best, Yu Ding On 2022/03/23 06:02:04 Yuan Zhuang wrote: > Hi all, > > I am pleased to be calling this vote for the second release of > Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 2). > > The release candidate to be voted over is available at: > - > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/ > > The release candidate is signed with a GPG key available at: > - https://downloads.apache.org/incubator/teaclave/KEYS > > The Git commit for this release is: > - > https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=9250da957b4c9dd9c916d582439cca28a359ec02 > > The release note is available in: > - > https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.2 > > Build guide and get started instructions can be found at: > - https://github.com/apache/incubator-teaclave-trustzone-sdk#readme > > The short version of building Teaclave TrustZone SDK from the source tarball: > > ``` > $ wget > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz > > # Instructions to verify the source tar: > # https://teaclave.apache.org/download/#verify-the-integrity-of-the-files > > $ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz && cd > apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating > > # Build the SDK and TAs > $ docker run -v$(pwd):/teaclave -w /teaclave -it > teaclave/teaclave-trustzone-sdk-build:0.3.0 bash -c "./setup.sh && source > environment && make" > > # Test all examples with QEMU > $ docker run -v$(pwd):/teaclave -w /teaclave -it > teaclave/teaclave-trustzone-sdk-build:0.3.0 bash -c "cd ci && ./ci.sh" > ``` > > The vote will be open for at least 72 hours. Everyone is welcome to vote. > Please vote by replying to this thread explicitly. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Anyone can participate in testing and voting, not 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 Regards, > > Yuan Zhuang > Apache Teaclave (incubating) Committer > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1
+1 Thanks Best, Yu On 2022/03/22 06:58:17 Mingshen Sun wrote: > Hi all, > > I am pleased to be calling this vote for the third release of > Apache Teaclave (incubating) 0.4.0 (release candidate 1). > > The release candidate to be voted over is available at: > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/ > > The release candidate is signed with a GPG key available at: > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS > > The Git commit for this release is: > - > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352 > > The release note is available in: > - https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0-rc.1 > > Build guide and get started instructions can be found at: > - > https://github.com/apache/incubator-teaclave/blob/v0.4.0-rc.1/docs/my-first-function.md > > The short version of building Teaclave from the source tarball: > > ``` > $ wget > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/apache-teaclave-0.4.0-rc.1-incubating.tar.gz > $ tar zxvf apache-teaclave-0.4.0-rc.1-incubating.tar.gz && cd \ > apache-teaclave-0.4.0-rc.1-incubating > $ # Instructions to verify the source tar: > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \ > -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \ > bash -c ". /root/.cargo/env && \ > . /opt/sgxsdk/environment && \ > mkdir -p build && cd build && \ > cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \ > make" > ``` > > The vote will be open for at least 72 hours. Everyone is welcome to > vote. Please vote by replying to this thread explicitly. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Anyone can participate in testing and voting, not 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, > > Mingshen Sun > Apache Teaclave (incubating) PPMC > https://mssun.me > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: [apache/incubator-teaclave-sgx-sdk] PanicInfo in sgx_tstd (Issue #375)
Closed #375. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/375#event-6245497194 You are receiving this because you are subscribed to this thread. Message ID:
[apache/incubator-teaclave-sgx-sdk] [WIP] v2.0.0 (PR #374)
You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/374 -- Commit Summary -- * v2.0.0-preview init * fix .gitignore * Update Readme.md -- File Changes -- M .gitignore (67) M LICENSE (40) A NOTICE (5) M README.md (334) D WORKSPACE (37) M buildenv.mk (38) D common/inc/complex.h (134) D common/inc/dirent.h (48) A common/inc/internal/arch.h (317) A common/inc/internal/cpuid.h (38) A common/inc/internal/cpuid_gnu.h (76) A common/inc/internal/inst.h (61) A common/inc/internal/metadata.h (211) A common/inc/internal/se_cdefs.h (96) A common/inc/internal/se_cpu_feature.h (47) A common/inc/internal/se_cpu_feature_defs.h (294) A common/inc/internal/se_cpu_feature_defs_ext.h (490) A common/inc/internal/se_types.h (93) A common/inc/internal/sgx_cet.h (70) A common/inc/internal/trts_inst.h (90) A common/inc/internal/tseal_migration_attr.h (53) A common/inc/internal/util.h (84) D common/inc/iso646.h (26) D common/inc/limits.h (41) D common/inc/math.h (430) D common/inc/netdb.h (41) D common/inc/poll.h (38) D common/inc/pwd.h (40) D common/inc/sched.h (62) D common/inc/setjmp.h (65) A common/inc/sgx.h (40) A common/inc/sgx_attributes.h (67) A common/inc/sgx_cpuid.h (57) A common/inc/sgx_dcap_key_exchange.h (77) A common/inc/sgx_dcap_tkey_exchange.h (209) A common/inc/sgx_dcap_tvl.h (93) A common/inc/sgx_defs.h (55) A common/inc/sgx_dh.h (196) A common/inc/sgx_ecp_types.h (60) A common/inc/sgx_edger8r.h (128) A common/inc/sgx_eid.h (39) A common/inc/sgx_error.h (127) A common/inc/sgx_intrin.h (64) A common/inc/sgx_key.h (97) A common/inc/sgx_key_exchange.h (89) A common/inc/sgx_lfence.h (47) A common/inc/sgx_pce.h (128) A common/inc/sgx_pcl_guid.h (63) A common/inc/sgx_ql_lib_common.h (210) A common/inc/sgx_ql_quote.h (84) A common/inc/sgx_quote.h (143) A common/inc/sgx_quote_3.h (193) A common/inc/sgx_qve_header.h (109) A common/inc/sgx_report.h (120) A common/inc/sgx_rsrv_mem_mngr.h (101) A common/inc/sgx_secure_align.h (154) A common/inc/sgx_secure_align_api.h (102) A common/inc/sgx_spinlock.h (53) A common/inc/sgx_tcrypto.h (1842) A common/inc/sgx_tkey_exchange.h (174) A common/inc/sgx_tprotected_fs.h (325) A common/inc/sgx_trts.h (98) A common/inc/sgx_trts_exception.h (151) A common/inc/sgx_tseal.h (259) A common/inc/sgx_ukey_exchange.h (342) A common/inc/sgx_urts.h (131) A common/inc/sgx_uswitchless.h (144) A common/inc/sgx_utils.h (110) D common/inc/signal.h (104) D common/inc/stdarg.h (48) D common/inc/stdio.h (95) D common/inc/stdlib.h (153) D common/inc/string.h (125) D common/inc/sys/_types.h (168) D common/inc/sys/cdefs.h (132) D common/inc/sys/epoll.h (42) D common/inc/sys/limits.h (77) D common/inc/sys/sockaddr.h (32) D common/inc/sys/socket.h (54) D common/inc/sys/stat.h (127) D common/inc/sys/struct_timespec.h (37) D common/inc/sys/types.h (129) D common/inc/sys/uio.h (35) D common/inc/time.h (105) R common/inc/tlibc/assert.h (0) A common/inc/tlibc/complex.h (134) R common/inc/tlibc/ctype.h (0) A common/inc/tlibc/dirent.h (75) R common/inc/tlibc/endian.h (0) R common/inc/tlibc/errno.h (0) A common/inc/tlibc/fcntl.h (73) A common/inc/tlibc/fenv.h (139) R common/inc/tlibc/float.h (0) R common/inc/tlibc/inttypes.h (0) A common/inc/tlibc/iso646.h (26) A common/inc/tlibc/limits.h (41) A common/inc/tlibc/math.h (430) R common/inc/tlibc/mbusafecrt.h (0) A common/inc/tlibc/netdb.h (53) A common/inc/tlibc/poll.h (47) A common/inc/tlibc/pthread.h (142) A common/inc/tlibc/pwd.h (42) A common/inc/tlibc/sched.h (71) A common/inc/tlibc/setjmp.h (65) A common/inc/tlibc/signal.h (124) A common/inc/tlibc/stdarg.h (48) R common/inc/tlibc/stdbool.h (0) R common/inc/tlibc/stddef.h (0) R common/inc/tlibc/stdint.h (0) A common/inc/tlibc/stdio.h (99) A common/inc/tlibc/stdlib.h (158) A common/inc/tlibc/string.h (125) A common/inc/tlibc/sys/_types.h (170) A common/inc/tlibc/sys/cdefs.h (132) R common/inc/tlibc/sys/endian.h (0) A common/inc/tlibc/sys/epoll.h (49) A common/inc/tlibc/sys/eventfd.h (39) A common/inc/tlibc/sys/fpu.h (99) R common/inc/tlibc/sys/ieee.h (0) A common/inc/tlibc/sys/ioctl.h (41) A common/inc/tlibc/sys/limits.h (77) A common/inc/tlibc/sys/prctl.h (38) A common/inc/tlibc/sys/random.h (43) A common/inc/tlibc/sys/sendfile.h (39) A common/inc/tlibc/sys/sockaddr.h (32) A common/inc/tlibc/sys/socket.h (89) A common/inc/tlibc/sys/stat.h (134) R common/inc/tlibc/sys/stdint.h (0) A common/inc/tlibc/sys/struct_timespec.h (37)
Re: [apache/incubator-teaclave-sgx-sdk] 1.1.4 enclave linker error undefined reference to `__assert_fail' without release (Issue #373)
@celaus reproduced. thanks! looks like the newer compiler somehow does not include `__assert_fail`'s implementation in generated static libraries. to this end, you can `export CFLAGS="-DRING_CORE_NOSTDLIBINC=1"` to let Ring build without the `__assert_fail` dependency. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/373#issuecomment-1035706472 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] 1.1.4 enclave linker error undefined reference to `__assert_fail' without release (Issue #373)
@celaus which rustc are you using? i just tested against nightly-2021-11-01 and didn't reproduce. $ rustc --version rustc 1.58.0-nightly (ff0e14829 2021-10-31) -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/373#issuecomment-1034399559 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Import asm macro (PR #372)
Merged #372 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/372#event-6022216073 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Updating rust toolchain to >2021-11-23 not possible (Issue #368)
Closed #368 via #370. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/368#event-6016041749 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Wrap next_code_point in unsafe block (PR #370)
Merged #370 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/370#event-6016041741 You are receiving this because you are subscribed to this thread. Message ID:
[apache/incubator-teaclave] fix: code coverage report generation (PR #611)
## Description Code coverage report generation has been stopped for a while due to toolchain upgrade. This PR fixes the report generation command `cmake -DCOV=ON` and `make cov` Please release a set of build image after the merge. Fixes # (issue) ## Type of change (select or add applied and delete the others) - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] API change with a documentation update - [ ] Additional test coverage - [x] Code cleanup or just sync with upstream third-party crates ## How has this been tested? Code coverage report has been generated successfully at https://gist.github.com/dingelish/186ecb02002bb273a47e0cbfd1196483 ## Checklist - [x] Fork the repo and create your branch from `master`. - [x] If you've added code that should be tested, add tests. - [x] If you've changed APIs, update the documentation. - [x] Ensure the tests pass (see CI results). - [x] Make sure your code lints/format. You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave/pull/611 -- Commit Summary -- * fix: code coverage report generation -- File Changes -- M cmake/scripts/gen_cov.sh (2) M docker/build.ubuntu-1804.sgx-2.14.Dockerfile (7) M docker/build.ubuntu-1804.sgx-dcap-1.11.Dockerfile (7) M docker/build.ubuntu-2004.sgx-2.15.1.Dockerfile (7) M docker/build.ubuntu-2004.sgx-dcap-1.12.1.Dockerfile (7) M third_party/crates-sgx (2) -- Patch Links -- https://github.com/apache/incubator-teaclave/pull/611.patch https://github.com/apache/incubator-teaclave/pull/611.diff -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/611 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave] fix link scripts (PR #610)
#581 has been closed for weeks. is this still needed? anything improved since then? -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/610#issuecomment-1029282935 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave] fix: code coverage report generation (PR #606)
rebased on #606 -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/606#issuecomment-1028511155 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave] Export TVM_HOME env var for prebuilt tvm-sys (PR #607)
Merged #607 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/607#event-5999604350 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave] fix: code coverage report generation (PR #606)
TVM build failed. Upstream fix is https://github.com/apache/tvm/pull/10147 -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/606#issuecomment-1028475218 You are receiving this because you are subscribed to this thread. Message ID:
[apache/incubator-teaclave] fix: code coverage report generation (PR #606)
## Description Code coverage report generation has been stopped for a while due to toolchain upgrade. This PR fixes the report generation command `cmake -DCOV=ON` and `make cov` Please release a set of build image after the merge. Fixes # (issue) ## Type of change (select or add applied and delete the others) - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] API change with a documentation update - [ ] Additional test coverage - [x] Code cleanup or just sync with upstream third-party crates ## How has this been tested? Code coverage report has been generated successfully at https://gist.github.com/dingelish/186ecb02002bb273a47e0cbfd1196483 ## Checklist - [x] Fork the repo and create your branch from `master`. - [x] If you've added code that should be tested, add tests. - [x] If you've changed APIs, update the documentation. - [x] Ensure the tests pass (see CI results). - [x] Make sure your code lints/format. You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave/pull/606 -- Commit Summary -- * fix: code coverage report generation -- File Changes -- M cmake/scripts/gen_cov.sh (2) M docker/build.ubuntu-1804.sgx-2.14.Dockerfile (7) M docker/build.ubuntu-1804.sgx-dcap-1.11.Dockerfile (7) M docker/build.ubuntu-2004.sgx-2.15.1.Dockerfile (7) M docker/build.ubuntu-2004.sgx-dcap-1.12.1.Dockerfile (7) M third_party/crates-sgx (2) -- Patch Links -- https://github.com/apache/incubator-teaclave/pull/606.patch https://github.com/apache/incubator-teaclave/pull/606.diff -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/606 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] fix: ci (PR #367)
Merged #367 into master. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/367#event-5811973114 You are receiving this because you are subscribed to this thread. Message ID:
[apache/incubator-teaclave-sgx-sdk] fix: ci (PR #367)
temporarily added a couple of issues to let cargo audit pass. will upgrade dependencies later. You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/367 -- Commit Summary -- * fix: ci build * fix: ci build * fix: ci build * fix: wasmi sample * fix: ci * fix: ci -- File Changes -- M .github/workflows/sgx-world.yml (16) M .github/workflows/sim-example.yml (24) M samplecode/wasmi/app/Cargo.toml (3) -- Patch Links -- https://github.com/apache/incubator-teaclave-sgx-sdk/pull/367.patch https://github.com/apache/incubator-teaclave-sgx-sdk/pull/367.diff -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/367 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Use simulation mode on MacOS (#318)
@Astewart1510 here you go https://github.com/apache/incubator-teaclave-trustzone-sdk -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/318#issuecomment-999773368 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Use simulation mode on MacOS (#318)
hi @Astewart1510 this is almost impossible. teaclave sgx sdk is built on top of intel sgx sdk which is x86 only. we can make rust part compile but i'm afraid we can't make intel sgx sdk compile on arm64. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/318#issuecomment-998992917 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave-sgx-sdk] Naming of Mutex (#356)
Mutex roots at os kernel provided primitives (like futex). But SgxMutex does not root at it. It's completely two different implementation with different assumptions (but with similar APIs) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/356#issuecomment-898612811
Re: [apache/incubator-teaclave-sgx-sdk] fix: correct buffer overwrite in sgx_libc::ocall::{read, pread64, readv, preadv64} (#353)
@volcano0dr please review. thanks! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/353#issuecomment-897327866
Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.1.0-rc1
+1 Yu On 2021/06/04 22:18:59, Mingshen Sun wrote: > Dear Teaclave community, > > I am pleased to be calling this vote for the first release of Apache > Teaclave TrustZone SDK (incubating) 0.1.0 (release candidate 1). > > The release candidate to be voted over is available at: > - > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.1.0-rc.1 > > The release candidate is signed with a GPG key available at: > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS > > The Git commit for this release is: > - > https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=8587ffca8d3dbed15d2a36ed7cd6a33b6efd8965 > > The release note is available in: > - > https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.1.0-rc.1 > > Build guide and get started instructions can be found at: > - > https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/v0.1.0-rc.1/README.md > > The short version of building and testing Teaclave TrustZone SDK from > the source tarball: > > ``` > $ wget > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.1.0-rc.1/apache-teaclave-trustzone-sdk-0.1.0-rc.1-incubating.tar.gz > $ tar zxvf apache-teaclave-trustzone-sdk-0.1.0-rc.1-incubating.tar.gz && cd > apache-teaclave-trustzone-sdk-0.1.0-incubating > > $ # Instructions to verify the source tar: > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files > > $ # Building > $ docker run --rm -it -v$(pwd):/teaclave-trustzone-sdk -w > /teaclave-trustzone-sdk teaclave/teaclave-trustzone-sdk-build:0.1.1 > bash -c "source environment && make" > > $ # Testing > $ docker run --rm -it -v$(pwd):/teaclave-trustzone-sdk -w > /teaclave-trustzone-sdk teaclave/teaclave-trustzone-sdk-build:0.1.1 > bash -c "source environment && cd ci && ./ci.sh" > ``` > > The vote will be open for at least 72 hours. Everyone is welcome to > vote. Please vote by replying to this thread explicitly. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Anyone can participate in testing and voting, not just committers, > please feel free to try out the release candidate and provide your > votes. > > A checklist for reference: > - > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > Note that you can also reply with things you have checked. > > Best, > > Mingshen Sun > http://mssun.me > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: [apache/incubator-teaclave-sgx-sdk] Will panicking inside of enclave code cause undefined behavior (#341)
hi @longtomjr ! we are aware of this UB since the first day we started this project. so by design, we do not allow any cross FFI-boundary unwinding. and we support Rust `catch_unwind` to handle exceptions within the Rust space. https://github.com/apache/incubator-teaclave-sgx-sdk/blob/master/samplecode/unit-test/enclave/src/test_exception.rs#L65 Intel SGX SDK never throw exceptions outside, so we're good and we don't catch Intel SGX SDK's C++ exceptions. I'm not clear if you are confusing between "the panic generated by CPU", and "panic generated by unwrap". please elaborate. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/341#issuecomment-849096081
Re: [apache/incubator-teaclave-sgx-sdk] added project template for easier use (#338)
Merged #338 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/338#event-4639467131
Re: [apache/incubator-teaclave-sgx-sdk] added project template for easier use (#338)
thanks guys! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/338#issuecomment-826027302
Re: [apache/incubator-teaclave-sgx-sdk] Implications of Upcoming Total Memory Encryption (TME) (#333)
here are some other contexts i have: 1. TME is total memory encryption, another memory encryption technology apart from [Intel SGX Memory Encryption Engine](https://software.intel.com/content/www/us/en/develop/blogs/memory-encryption-an-intel-sgx-underpinning-technology.html). 2. Differences between TME and SGX MEE: SGX MEE guarantees memory integrity by maintaining a merkle tree. meanwhile the depth of the merkle tree limits the size of EPC; TME does not guarantee memory integrity (1st generation of TME) so EPC size limit is significantly higher than SGX MEE. 3. Intel SGX v2 (upcoming in icelake+whitley) uses MKTME, Multi-Key TME 4. Intel TDX, as a competitor of AME SEV, uses MKTME as well: https://software.intel.com/content/www/us/en/develop/articles/intel-trust-domain-extensions.html -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/333#issuecomment-811551039
Re: [apache/incubator-teaclave-sgx-sdk] Implications of Upcoming Total Memory Encryption (TME) (#333)
according to what i've known, no major changes in this sdk. things should work smoothly except the attestation procedure. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/333#issuecomment-811269507
Re: [apache/incubator-teaclave-sgx-sdk] Rls not finding sgx_tstd in VS Code within Docker image (#334)
hi @dhuynh95 , this could be a bug of rls or misconfiguration of rls, but i'm not familiar with rls and vscode so can't give you a precise solution. i looked into such issues in the past and had this [note](https://github.com/apache/incubator-teaclave-sgx-sdk/wiki/Use-VSCode---rls---rust-analysis---sgx-gdb-for-graphic-developing-(not-in-docker)) . wish it helps ... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/334#issuecomment-811268757
Re: [apache/incubator-teaclave-sgx-sdk] Possibility to implement tensorflow/keras in sgx (#335)
thanks for the pointer! i've been watching on tf's sgx support for quite a while. as of today i still believe libtensorflow-sys is the core problem. 2 years ago i looked into tf-lite and iirc my conclusion was that tf-lite could be ported with minimal changes. but i haven't got time for that since then ... if you want to run full functional tf, another option is to use libOS, such as graphene. I know a couple of companies including Intel are trying to do so. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/335#issuecomment-811267186
Re: [apache/incubator-teaclave-sgx-sdk] multiple definition of '_U_dyn_info_list' when trying to compile (#313)
@assafmo @cschramm i think https://github.com/apache/incubator-teaclave-sgx-sdk/pull/329 solve this. could you please test it? thank you! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/313#issuecomment-805229103
Re: [apache/incubator-teaclave-sgx-sdk] Fix samplecode compiler error with newer GCC. (#329)
@yuguorui thank you so much! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/329#issuecomment-805227235
Re: [apache/incubator-teaclave-sgx-sdk] Fix samplecode compiler error with newer GCC. (#329)
Merged #329 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/329#event-4498399082
Re: [apache/incubator-teaclave-sgx-sdk] multiple definition of '_U_dyn_info_list' when trying to compile (#313)
Closed #313 via #329. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/313#event-4498399094
Re: [apache/incubator-teaclave-sgx-sdk] Benchmarking / Profiling Recommendations (#330)
hi @LeibnizCapital , we have some benchmark results in our CCS'19 paper: https://dingelish.com/ccs19.pdf . section 7 testing code is at https://github.com/mesalock-linux/rust-sgx-benchmark -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/330#issuecomment-805226191
Re: [apache/incubator-teaclave-sgx-sdk] Local attestation Shared library (#328)
@blmalone no worries. i'll get this done in 1~2 days :-) but i don't have the latest "localattestation" similar to Intel's sample right now. the current local attestation is a Rust implementation of a very early version of Intel's local attestation sample. I'll have a summer intern who will work on the upgrade but i guess it's late for you :-( -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/328#issuecomment-804536064
Re: [apache/incubator-teaclave-sgx-sdk] Local attestation Shared library (#328)
Regarding to the missing macro definition `println!` please add `#[macro_use]` before you do `extern crate sgx_tstd as std`. reference: https://github.com/apache/incubator-teaclave-sgx-sdk/blob/master/samplecode/hello-rust/enclave/src/lib.rs#L26 the reason is that by default, rust brings these on a regular `.rs` file (without `no_std` or `no_core`) ```rust #[macro_use] extern crate std; use std::prelude::v1::*; ``` to import `sgx_tstd` you need to (on a 2015-styled crate) and using cargo (not xargo): 1. `#[macro_use] extern crate sgx_tstd as std` in `lib.rs` only 2. `use std::prelude::v1::*` in every `.rs` where you need functions exported by std; -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/328#issuecomment-804329584
Re: [apache/incubator-teaclave-sgx-sdk] Fix link to http_req-sgx (#327)
Merged #327 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/327#event-4473229967
Re: [apache/incubator-teaclave-sgx-sdk] Fix link to http_req-sgx (#327)
thanks @Trundle ! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/327#issuecomment-801536390
Re: [apache/incubator-teaclave-sgx-sdk] Incompatible with hashbrown 0.11 (#326)
Hi @xu-cheng , thanks for your report. I totally agree on every word you mentioned above. maintain a bunch of forked crates can help us with (1) stability and (2) compatibility and (3) features, and something suffers a lot (1) freshness, (2) security. but overall I slightly intended to maintain an isolated ecosystem. and in production, i believe most products vendor their dependencies and then maintain their vendored sources. on the getrandom issue, i'd say the only doable way is to maintain a fork of getrandom. as you already know, quality of random number is **critical** to Intel SGX enclaves, while it may not mean much to many of other platforms. getrandom lays on the bottom of the entire crate dependency graph and i'd strongly recommend user to maintain their own fork. and i believe hashbrown is a very very special case: std has a built-in hashbrown (v0.9.0 as of today). and one principle you may know is "we should not have 2 different versions of the same library in the same dependency tree". so I'd say if you need hashbrown, first try if you can use the libstd's built-in one. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/326#issuecomment-800799978
Re: [apache/incubator-teaclave-sgx-sdk] WIP - feat(sgx_types): add traits using derive (#325)
thanks man! i have a `debug_types` branch out there for your reference. iirc i put a proc macro to simplify the work. however, it made the sgx_types crate depends on something. this is not what i desired. so i stopped merge that. if we can implement Debug for all of the types including types with large arrays, it's really really helpful. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/325#issuecomment-797802125
Re: [apache/incubator-teaclave-sgx-sdk] upgrade mesalock-linux / log-sgx to v0.4.14 (#323)
@haerdib updated! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/323#issuecomment-796500043
Re: [apache/incubator-teaclave-sgx-sdk] fix: add pointer null check on ecall function (#322)
Merged #322 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/322#event-4434337117
Re: [apache/incubator-teaclave-sgx-sdk] DCAP Error (#321)
I think i5-7300u does not support DCAP, which requires Flexible Launch Control (a hardware feature). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/321#issuecomment-794460899
Re: [apache/incubator-teaclave-sgx-sdk] DCAP Error (#321)
please refer to the readme for setup :-) https://github.com/apache/incubator-teaclave-sgx-sdk/blob/master/samplecode/dcap-pckretrieval/Readme.md for the apt commands, since intel just released 2.13, i recommend force the version number by ``` sudo apt install libsgx-dcap-ql=1.9.100.3-bionic1 libsgx-ae-qve=1.9.100.3-bionic1 libsgx-dcap-quote-verify=1.9.100.3-bionic1 ``` `1.9.100.3` is the one currently supported by this sdk (v1.1.3) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/321#issuecomment-792971470
Re: [apache/incubator-teaclave-sgx-sdk] DCAP Error (#321)
fix is involved in PR #322 :-) will be merged shortly -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/321#issuecomment-792461008
Re: [apache/incubator-teaclave-sgx-sdk] fix: add pointer null check on ecall function (#322)
@pedrotbtl @woloszyn please take a look. thanks! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/322#issuecomment-792397790
[apache/incubator-teaclave-sgx-sdk] fix: add pointer null check on ecall function (#322)
reported by @pedrotbtl and @woloszyn . thanks for contribution! You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/322 -- Commit Summary -- * fix: add pointer null check on ecall function -- File Changes -- M samplecode/http_req/enclave/src/lib.rs (4) M samplecode/tls/tlsclient/enclave/src/lib.rs (4) M sgx_tstd/src/rt.rs (4) -- Patch Links -- https://github.com/apache/incubator-teaclave-sgx-sdk/pull/322.patch https://github.com/apache/incubator-teaclave-sgx-sdk/pull/322.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/322
Re: [apache/incubator-teaclave-sgx-sdk] bug fix call sched_getaffinity result segment fault (#320)
@volcano0dr please help. thanks! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/320#issuecomment-790283537
Re: [apache/incubator-teaclave-sgx-sdk] multiple definition of '_U_dyn_info_list' when trying to compile (#313)
thanks @okready ! let me try to reproduce this and see if we can port that commit to our fork :-) thanks again! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/313#issuecomment-776474303
Re: [apache/incubator-teaclave-sgx-sdk] fix(sgx_types): correct improper c-types (#316)
@volcano0dr please help :-) thanks! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/316#issuecomment-776473708
Re: [apache/incubator-teaclave-sgx-sdk] Support stable rust? (#315)
Hi @xu-cheng please checkout beta/stable support at https://github.com/apache/incubator-teaclave-sgx-sdk/tree/stable-support -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/315#issuecomment-775666315
Re: [apache/incubator-teaclave-sgx-sdk] Support stable rust? (#315)
thanks @xu-cheng for the pointer! the sad fact is that: people wants std here :-( that's why things are so complicated. and std-aware cargo is sometimes buggy :-( only `no_std` make things clean and tidy. but we don't have this choice. I'd try to support both stable and nightly in the same branch. but I do have users who wants to always keep updated with latest nightly. and recent frequent breaking changes in `libcore::alloc` make things much more complicated than before. I want to make every one happy but it's bit of hard :-( -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/315#issuecomment-775654796
Re: [apache/incubator-teaclave-sgx-sdk] Support stable rust? (#315)
> As far as I understand, there are two ways to use this SDK to write enclave
> codes: (a) build SGX's version of the std and use it normally; (b) write the
> enclave codes in no_std.
Yes you are correct. But both of them are *logically building a sysroot*, so I
don't recommend to use stable Rust.
> Can stable rust be used if the second way is used? Here we don't need to deal
> with xcargo or std aware cargo. Or am I understanding incorrectly?
Yes you can. Just make sure `${projectroot}/rust-toolchain` 's content is
something like `stable-2020-xx-xx` or `stable` and export `RUSTC_BOOTSTRAP=1`.
I'm not sure if current code can be built successfully. But if you need, I can
create a branch to support you. Please specify the stable toolchain you want to
use and I'd be working on that.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/315#issuecomment-775649098
Re: [apache/incubator-teaclave-sgx-sdk] Support stable rust? (#315)
If you look at `xargo` and `cargo-xbuild`, you'll find that the community has reached to consensus to build `std`s with nightly toolchain https://github.com/rust-osdev/cargo-xbuild/pull/53 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/315#issuecomment-775634347
Re: [apache/incubator-teaclave-sgx-sdk] Support stable rust? (#315)
Hi @xu-cheng , Rust builds itself by using `beta` toolchain with backdoor environment variable `RUSTC_BOOTSTRAP=1`, which enables **all nightly feature gates** in beta channel. It's almost equivalent to nightly compiler. As a consequence, using stable channel Rust compiler with `RUSTC_BOOTSTRAP=1` feature is doable, but does not benefit at all. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/315#issuecomment-775633171
Re: [apache/incubator-teaclave-sgx-sdk] multiple definition of '_U_dyn_info_list' when trying to compile (#313)
@assafmo can i have your `./lib/libenclave.a` ? thanks! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/313#issuecomment-774225419
Re: [apache/incubator-teaclave-sgx-sdk] multiple definition of '_U_dyn_info_list' when trying to compile (#313)
seems multiple `libunwind` are involved. let me investigate. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/313#issuecomment-774219372
Re: Teaclave meetup
no worry. it's tomorrow. On Wed, Jan 27, 2021 at 18:19 rduan wrote: > Please send me a zoom link for teaclave meetup. Thanks! > > >
Re: [apache/incubator-teaclave-sgx-sdk] Using std Aware Cargo (#311)
@mssun thanks! i'll create a branch for rust-sgx-sdk, based on your build-std repo :-) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/311#issuecomment-755097386
Re: [VOTE] Accept Rust OP-TEE TrustZone SDK to Apache Teaclave (incubating)
+1 Best, Yu On 2021/01/04 23:43:00, Mingshen Sun wrote: > Hi all, > > Rust OP-TEE TrustZone SDK provides abilities to build safe TrustZone > applications in Rust. The SDK is based on the OP-TEE project which > follows GlobalPlatform TEE specifications and provides ergonomic APIs. > > The SDK was developed by Baidu and open source on Jan 30, 2019. I'm > one of the initial comitters of the project. > > On behalf of the Rust OP-TEE TrustZone SDK project, I would like to > call a VOTE to accept Rust OP-TEE TrustZone SDK into Apache Teaclave > (incubating) as a subproject. I'm using part of the incubator proposal > template, but omit some irrelevant sections. > > Please cast your vote: > > [ ] +1, bring Rust OP-TEE TrustZone SDK into Teaclave > [ ] +0, I don't care either way > [ ] -1, do not bring Rust OP-TEE TrustZone SDK into Teaclave, because... > > The vote will open at least for 72 hours and only votes from the > Teaclave PPMC are binding, but votes from everyone are welcome. > > Proposal === > > ## Abstract > > Rust OP-TEE TrustZone SDK provides abilities to build safe TrustZone > applications in Rust. The SDK is based on the OP-TEE project which > follows GlobalPlatform TEE specifications and provides ergonomic APIs. > More information can be found at the project repository: > https://github.com/sccommunity/rust-optee-trustzone-sdk. > > ## Proposal > > Rust OP-TEE TrustZone SDK provides abilities to build safe TrustZone > applications in Rust. > > ### Background > > The Rust OP-TEE TrustZone project is being actively developed within > Baidu. It was open source on Jan 30, 2019. > > ### Rationale > > ARM TrustZone is another hardware trusted execution environment > implementation. The goal of Teaclave is to provide a universal secure > computing platform which is agnostic with TEE implementation. > Currently, Teaclave has Teaclave SGX SDK and only supports Intel SGX. > With the Rust OP-TEE TrustZone SDK, we can build the Teaclave platform > on ARM TrustZone. > > ### Initial Goals > > - Transfer repository to the Apache Incubator under the Teaclave project > - Code cleanup and more documentation > > Meritocracy: > > The Rust OP-TEE TrustZone SDK project was originally developed by > Shengye Wan and Mingshen Sun within Baidu. The project now has new > committers from around the world. Some open source projects like > https://github.com/veracruz-project are using the SDK to build their > systems. We encourage everyone to ask questions and create pull > requests to the project. > > Community: > > We see several open source projects which are using the SDK for > development. Also, we already receive contributions from external > comitters. The community is growing overtime. > > Core Developers: > > The core developers are: > - Shengye Wan (simonsywan at gmail dot com) > - Mingshen Sun (mssun at apache.org) > > Alignment: > > The project is a complimentary of Teaclave's TEE backends. > > ### Known Risks > > An exercise in self-knowledge. Risks don't mean that a project is > unacceptable. If they are recognized and noted, then they can be > addressed during incubation. > > Project Name > > Since the project will be accepted as a subproject in Teaclave, the > project is renamed to Teaclave TrustZone SDK. > > Inexperience with Open Source: > > One of the core developers, Mingshen Sun is from the Teaclave > community. He's familiar with The Apache Way for the open source > community. > > Length of Incubation: > > The project will be in incubation with Apache Teaclave (incubating) project. > > ### Documentation > > - > https://github.com/sccommunity/rust-optee-trustzone-sdk/wiki/Getting-started-with-OPTEE-for-QEMU-ARMv8 > > ### Initial Source > > - https://github.com/sccommunity/rust-optee-trustzone-sdk > > ### Source and Intellectual Property Submission Plan > > We will submit a Software Grant for this project later. > > External Dependencies: > > The dependencies have Apache compatible license, which is provided > under the BSD 2-Clause license. > > Cryptography: > > N/A > > ### Required Resources > > Mailing lists: > > The project shares the same mailing list of Teaclave. > > Git Repositories: > > - https://gitbox.apache.org/repos/asf/incubator-teaclave-trustzone-sdk.git > - https://github.com/apache/incubator-teaclave-trustzone-sdk > > Issue Tracking: > > Same with Teaclave. > > Other Resources: > > N/A > > ### Initial Committers > > - Shengye Wan (simonsywan at gmail dot com) > - Mingshen Sun (mssun at apache dot org) > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional comma
Re: [apache/incubator-teaclave-sgx-sdk] Is there any tool for enclave memory measurement? (#310)
Closed #310. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/310#event-4166176502
Re: [apache/incubator-teaclave-sgx-sdk] Is there any tool for enclave memory measurement? (#310)
please check out https://download.01.org/intel-sgx/sgx-linux/2.12/docs/Intel_SGX_Developer_Reference_Linux_2.12_Open_Source.pdf page 25 Enclave Memory Measurement Tool An enclave is an isolated environment. The Intel® Software Guard Extensions SDK provides a tool called sgx_emmt to measure the real usage of protected memory by the enclave at runtime. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/310#issuecomment-754140049
Re: [apache/incubator-teaclave-sgx-sdk] Encrypted websockets in SGX (#291)
@celaus wireshark guided me to this answer 😂 https://github.com/ctz/rustls/issues/381 echo.websocket.org only supports `TLS_RSA_WITH_AES_128_CBC_SHA` which is not supported by `rustls`. shall we try another wss echo server? ``` nmap --script ssl-enum-ciphers -p 443 echo.websocket.org Starting Nmap 7.91 ( https://nmap.org ) at 2020-12-30 14:11 PST Nmap scan report for echo.websocket.org (174.129.224.73) Host is up (0.080s latency). rDNS record for 174.129.224.73: ec2-174-129-224-73.compute-1.amazonaws.com PORTSTATE SERVICE 443/tcp open https | ssl-enum-ciphers: | TLSv1.2: | ciphers: | TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A | compressors: | NULL | cipher preference: indeterminate | cipher preference error: Too few ciphers supported | warnings: | Forward Secrecy not supported by any cipher |_ least strength: A Nmap done: 1 IP address (1 host up) scanned in 5.13 seconds ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/291#issuecomment-752774468
Re: [apache/incubator-teaclave-sgx-sdk] Encrypted websockets in SGX (#291)
> Hi! Thank you for your support. I can confirm that your sample seems to > reproduce the error. > is it a bug of `echo.websocket.org`? or misconfiguration of `rustls`? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/291#issuecomment-752735078
Re: [apache/incubator-teaclave-sgx-sdk] Any plan to update sgx_cov (#306)
Closed #306. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/306#event-4158074706
Re: [apache/incubator-teaclave-sgx-sdk] Any plan to update sgx_cov (#306)
it's done! please checkout the latest sgx-cov sample! closed by #307 and #309 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/306#issuecomment-752718141
Re: [apache/incubator-teaclave-sgx-sdk] Fix sgx cov (#309)
Merged #309 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/309#event-4158073245
Re: [apache/incubator-teaclave-sgx-sdk] Any plan to update sgx_cov (#306)
@henrysun007 almost there! please checkout https://github.com/apache/incubator-teaclave-sgx-sdk/pull/309 . the only problem now is xargo support. cargo works perfectly with `gcov` <= 7 and `llvm-cov` >= 11 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/306#issuecomment-752294328
Re: [apache/incubator-teaclave-sgx-sdk] WIP: Fix sgx cov (#309)
@volcano0dr please help on xargo support. currently sgx-cov sample does not compile on `XARGO_SGX=1 make COV=1`: ``` error: the crate `panic_abort` does not have the panic strategy `abort` ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/309#issuecomment-752288255
[apache/incubator-teaclave-sgx-sdk] WIP: Fix sgx cov (#309)
changes: - fixed sgx_cov in `nightly-2020-10-25`, which provides `llvm-cov-11` - probe `gcov` and `llvm-cov` version heuristically. `gcov` <= 7 and `llvm-cov` >= 11 supported You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/309 -- Commit Summary -- * fix sgx-cov to be compatible with LLVM 10 profiler API * Update readme. add gcov version requirement * temp fail cannot find final.info * cov: fix Makefile and support llvm-cov-12 -- File Changes -- M samplecode/sgx-cov/Makefile (1) M samplecode/sgx-cov/Readme.md (16) M samplecode/sgx-cov/enclave/enclave-cov-rustc (0) M samplecode/sgx-cov/enclave/llvm-gcov (57) M sgx_cov/lib.rs (237) -- Patch Links -- https://github.com/apache/incubator-teaclave-sgx-sdk/pull/309.patch https://github.com/apache/incubator-teaclave-sgx-sdk/pull/309.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/309
Re: [apache/incubator-teaclave-sgx-sdk] Any plan to update sgx_cov (#306)
@volcano0dr please help trigger `uninit_global_object` in `t_global_exit_ecall` and make it feature gated, since we need to remove it after `edmm` is public available. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/306#issuecomment-751581980
Re: [apache/incubator-teaclave-sgx-sdk] Any plan to update sgx_cov (#306)
never mind. i got the changes. will work on it. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/306#issuecomment-751573793
Re: [apache/incubator-teaclave-sgx-sdk] Any plan to update sgx_cov (#306)
and could you please give some hint on upstream llvm's change? documents/commit id will be helpful. thanks! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/306#issuecomment-751569642
Re: [apache/incubator-teaclave-sgx-sdk] Any plan to update sgx_cov (#306)
hi @henrysun007 , thanks for this report! yes it should be a bug. we'll definitely fix that. but no eta yet... i'll look into it whenever i've got time -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/306#issuecomment-751569389
Re: [apache/incubator-teaclave-sgx-sdk] help forking jsonrpc (#304)
hi @brenzi , i just got your `no_std` branch works along with substratee enclave. please review and merge https://github.com/scs/jsonrpc/pull/1 and then checkout my changes at https://github.com/dingelish/encointer-worker/commit/69bd8690eeb904fe201b713190fe7b139d00704c will look into the jsonrpc crates later ... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/304#issuecomment-751427083
Re: [apache/incubator-teaclave-sgx-sdk] Encrypted websockets in SGX (#291)
@celaus Hi there, i reproduced the error in non-sgx environment: https://github.com/dingelish/embedded-websocket ``` cargo r --example client ``` could you please advise how to make my fork's client example work? if it works, i'll get it work in SGX enclave :-) thanks! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/291#issuecomment-751311886
Re: [apache/incubator-teaclave-sgx-sdk] help forking jsonrpc (#304)
sure. do you need `jsonrpc-core` only? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/304#issuecomment-749220156
Re: [apache/incubator-teaclave-sgx-sdk] Are git tags being mutated? (#303)
hey @adaszko , unfortunately this is intentional for some bug fixes... the root problem is the bad "dependency resolver" built-in with cargo, which mess up many things when using git repo as dependency. cargo is now testing on the `v2 resolver`: https://github.com/rust-lang/cargo/issues/8088 once it got stabilized, we'll follow up and improve our sdk versioning. sorry for the inconvenient. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/303#issuecomment-749219422
Re: [apache/incubator-teaclave-sgx-sdk] upgrade serde_json to v1.0.60 (#302)
completed! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/302#issuecomment-748367843
Re: [apache/incubator-teaclave-sgx-sdk] upgrade serde_json to v1.0.60 (#302)
@haerdib upgraded. please check it out! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/302#issuecomment-747656032
Re: [apache/incubator-teaclave-sgx-sdk] upgrade serde_json to v1.0.60 (#302)
no problem! thanks for your support :-) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/302#issuecomment-747565901
Re: [apache/incubator-teaclave-sgx-sdk] SGX_RSA3072_DEFAULT_E has different value from documented one. (#296)
Closed #296. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/296#event-4122069560
Re: [apache/incubator-teaclave-sgx-sdk] chore(samplecode): init test input for wasmi from makefile (#300)
Merged #300 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/300#event-4122067957
