[GitHub] [incubator-teaclave-website] henrysun007 merged pull request #23: Update the official website
henrysun007 merged PR #23: URL: https://github.com/apache/incubator-teaclave-website/pull/23 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-trustzone-sdk] henrysun007 commented on issue #106: API doc links broken
henrysun007 commented on issue #106: URL: https://github.com/apache/incubator-teaclave-trustzone-sdk/issues/106#issuecomment-1592423713 I have uploaded the documents to the website in https://github.com/apache/incubator-teaclave-website just now. Please check the links out. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] henrysun007 opened a new pull request, #23: Update the official website
henrysun007 opened a new pull request, #23: URL: https://github.com/apache/incubator-teaclave-website/pull/23 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[apache/incubator-teaclave-sgx-sdk] More documents are needed for branch v2.0.0 (Issue #438)
-- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/438 You are receiving this because you are subscribed to this thread. Message ID:
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 > >
[apache/incubator-teaclave] Enabling access control service (Issue #700)
### Motivation & problem statement The access service is not used by any other services. The python engine (MesaPy) it uses is not maintained any more. Teaclave is moving towards Confidentail VM and the ported services should be determined. ### Proposed solution I reviewd all the access control code in the managment and frontend services and found that most of the access control patterns are attribute-based, like checking the user ID against the owner ID of the object, e.g., task, file and function. Three years ago, someone suggested using [casbin-rs](https://github.com/casbin/casbin-rs) as the engine in #265 . Casbin is powerful and supports ABAC. We can use it to do most of the access control. For more complicated access control, we can keep the enforcer hard-coded as it is now. Please feel free to comment, thanks. @mssun @uraj -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/700 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave] [RFC] Release Plan in 2023 Q2 (Issue #680)
Hanlding multiple tasks in one execution service faces isolation issues, so we keep the current single task handling. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/680#issuecomment-1590888736 You are receiving this because you are subscribed to this thread. Message ID:
