+1
Thanks!
On Wed, May 8, 2024 at 9:50 PM Mingshen Sun wrote:
> +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
> >
+1 approve
On Fri, May 12, 2023 at 11:33 AM Yu Ding wrote:
> +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
+1
- Qinkun
On Mon, Mar 27, 2023 at 7:50 PM Mingshen Sun wrote:
> +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).
>
+1. I endorse the graduation of Teaclave from the Apache Incubator.
On Mon, Jan 30, 2023 at 5:52 PM Gao,Yingchun(BS)
wrote:
> +1, I support the Teaclave project to graduate from the Apache Incubator.
>
> -邮件原件-
> 发件人: Gordon
> 发送时间: 2023年1月29日 12:20
> 收件人: dev@teaclave.apache.org
> 主题:
Hi all,
CCC is hosting a weekly meeting about the attestation. Here is the link
https://docs.google.com/document/d/1NkiS78knPhDO0vA9ElS-bQOHNu783gGPdmTEbbOoOOU/edit?usp=sharing
Some topics are related to Teaclave, such as RA-TLS. Everyone is welcome to
attend.
Thanks,
Qinkun
+1
On Tue, Oct 18, 2022 at 9:30 PM Yu Ding wrote:
> +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
As far as I know, there is no such plan at the moment.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/656#issuecomment-1279814176
You are receiving this because you are subscribed to this thread.
Message ID:
> How is the mesapy binary relocation? The project is not compilable now.
Here is the link https://github.com/mesalock-linux/mesapy
You may build it by setting the applying mesapy prebuilt option 'OFF'
> In your example, assigning the value of `env` to `sgx` dose work, but in some
> crates that depend on `libc`, it may cause the detection `target_env` to
> fail. For the processing of the CPUID instruction, you can refer to the
> example code
>
LGTM. Thanks!
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/654#issuecomment-1186283648
You are receiving this because you are subscribed to this thread.
Message ID:
> @mssun That is the same problem that I had and we commented previously on
> discord
> (https://discord.com/channels/891067964743376906/891068072503410738/944151562765361192)
Hi Torvel, thank you for bringing up the issue. We have an internal version of
Teaclave, and it works perfectly on
To follow the inclusive language best practice, we should rename the default
branch to main.
URL:
https://github.com/github/renaming
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/647
You are receiving this because you are subscribed
My experience (could be wrong)
1. If a program is CPU-intensive, the average overhead is 30% to 50%
2. If a program uses main memory a lot (e.g., the size of allocated memory is
larger than the EPC size), the program may have thousands of performance
penalties.
--
Reply to this email directly
Here is a tutorial.
https://github.com/dingelish/SGXfail/blob/master/04.md
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/597#issuecomment-1107688872
You are receiving this because you are subscribed to this thread.
Message ID:
I think the issue is fixed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/613#issuecomment-1083934642
You are receiving this because you are subscribed to this thread.
Message ID:
## Description
https://asciinema.org/a/9pStDa5jVGJegkAhXF1jZF74l
Fix incorrect error messages Error: No such volume: aesmd-socket
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/643
-- Commit Summary --
* Update
> @qinkunbao no lucky with IAS setup (is there any proxy setting to be
> considered), where can I find the log?
https://asciinema.org/a/9pStDa5jVGJegkAhXF1jZF74l
--
Reply to this email directly or view it on GitHub:
Hi Andy, thank you for using Apache Teaclave.
Yes, you cannot start the service unless you build Teaclave in the simulation
mode (`cmake -DSGX_SIM_MODE=ON -DTEST_MODE=ON ..`).
You can run `export TEACLAVCE_LOG=info` before starting the services. It will
enable the logs and provide more info.
## Description
This PR removes some magic numbers in Teaclave Python SDK.
## Checklist
- [x] Fork the repo and create your branch from `master`.
- [x] If youve added code that should be tested, add tests.
- [x] If youve changed APIs, update the documentation.
- [x] Ensure the tests pass (see CI
## Description
Fix typos in sdk.
## Type of change (select or add applied and delete the others)
- [ ] 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
`list_functions` and `get_function` have different access controls. For example,
`list_functions` allows `PlatformAdmin` to get every available functions stored
in the database.
Teaclave platform supports four different roles: DataOwner, DataOwnerManger,
FuntionOwer, and PlatformAdmin. Different roles have different permissions The
current functional testing only one role: PlatformAdmin. We need to add other
types of clients in the future.
--
Reply to this email
## Description
This PR adds a new feature called `disable function`. It allows function owners
to disable a function by specifying a function id. After that, data owners
cannot create a new task with this function id.
## Type of change (select or add applied and delete the others)
- [ ] Bug
Closed #610.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/610#event-6022838991
You are receiving this because you are subscribed to this thread.
Message ID:
This PR seems to be a temporary solution. We will refactor the build system in
the future.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/610#issuecomment-1032017517
You are receiving this because you are subscribed to this thread.
## Description
The execution service will only be terminated if the task status is `Running`.
This PR fixes the test in `mesapy_deadloop_cancel.py`.
## Type of change (select or add applied and delete the others)
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature
We should have a style guide for bash scripts.
As discussed in https://github.com/apache/incubator-teaclave/pull/609,
environment variables and internal shell variables are capitalized. All other
variable names should be lower case. Some shell scripts in the project don't
follow this
> I suggest to wrap C APIs into a struct and use `new` and `drop` for resource
> management.
Sounds good! Will do.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/608#issuecomment-1029456173
You are receiving this because you are
## Description
As discussed in #581, every service links `Mesapy` and `WAMR` into the
`enclave.so`. While most linkers avoid linking unneeded static objects, it is
not true for some libraries (e.g., sgx_trts).
`-Wl,-whole-archive library-include-runtime.a -Wl,-no-whole-archive`
Fixes #581
## Description
fix ide scripts; users can run ide.sh from any cwd
## 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
## Description
1. Update WAMR dependencies.
2. Remove assert and unwrap.
## 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
> Please rebase to the latest master for CI checking.
Done.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/603#issuecomment-1028618579
You are receiving this because you are subscribed to this thread.
Message ID:
## Description
`ResetUserPasswordResponse` is defined as
```Protobuf
message ResetUserPasswordResponse {
string password = 1;
}
```
https://github.com/apache/incubator-teaclave/blob/55e658d96b92389cb8bd203640432c9493711dd3/services/proto/src/proto/teaclave_authentication_service.proto#L81
## Description
This PR introduces optional input/output files.
For some tasks in biometric computing, the number of input/output files varies
case by case. Therefore, this PR adds a new feature called optional files. Once
a file is marked with `option: True`, users do not need to register the
## Description
Teaclave execution crate exports several APIs such as `reset_thread_context`,
`reset_thread_context`, and `c_open_input`. These APIs are used by statically
linked non-rust executors like `mesapy` and `wamr` to read/write files from the
execution service.
However, the above APIs
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/572
-- Commit Summary --
* https://github.com/apache/incubator-teaclave/pull/572/commits/db2942095a1a578771aa67394071b9078e0a0fa0;>Update
report_bug.md
-- File Changes --
> Good to see unloading the WASM's workload gracefully by adding corresponding
> native callbacks and preventing resource from leaking. However, there is a
> following issue identified by CI
>
> ```
> thread '' panicked at 'assertion failed: self.buffer.is_empty() ||
>
## Description
This PR fixes the resource leaks in WAMR.
https://github.com/bytecodealliance/wasm-micro-runtime/blob/51a00a4c2b60e50ae76ccd54c9f0db1c23555168/product-mini/platforms/posix/main.c#L443
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- Bug fix
Most Unix-style OSs are case-sensitive in file names, meaning that a folder
called `KEYs` is different from a file named `keys`.
However, Mac OS is not case-sensitive. So whenever developers clone a new repo,
the system will delete the folder `keys`, and a freshly cloned repo may look
messy.
## Description
Fix instructions to use ./run-teaclave-services.sh -m sim in simulation mode.
Fixes #562
Bug fix (non-breaking change which fixes an issue)
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/566
-- Commit Summary
Thank you! I will update the document 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/issues/562#issuecomment-935615235
I built teaclave in **simulation** mode, following the instruction from
https://github.com/apache/incubator-teaclave/blob/master/docs/my-first-function.md
When I tried to launch Teaclave services, I encountered the following error.
```
$ (cd docker && ./run-teaclave-services.sh)
/dev/isgx
Hi Mingshen,
Can I get the Zoom link? Thank you.
Qinkun
On Fri, Jul 23, 2021 at 12:00 AM Mingshen Sun wrote:
> Hi Gordon, I have sent it to you privately via email.
>
> For others, please also reply in this thread for the Zoom link.
> Because of some security concerns, I don't plan to public
Hi Mingshen,
I am interested in the meetup. Could you please send me the zoom link?
Thanks,
Qinkun
On Sun, Jan 24, 2021 at 6:36 PM Mingshen Sun wrote:
> Hi all,
>
> After investigations, I didn't find a recommended video conferencing method
> from ASF.
>
> Therefore, I decided to use Zoom for
可以单独编译teaclave_cli
`$ cd cli`
`$ cargo build`
--
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/issues/400#issuecomment-668952304
Without explicitly specifying the name of the argument, the value `message`
will pass to `payload_file`, not `message`.
CI: http://ci.mesalock-linux.org/qinkunbao/incubator-teaclave/70/1/5
You can view, comment on, or merge this pull request online at:
我最近也在看SGX，这是我的理解。如有不对欢迎指出来。
A <-> B
假设A是Client，B是encalve里面的代码，首先你信任client，因为这是在你本地上的，换言之这是你自己。B是Teaclave，但是你怎么需要保证Teaclave是你相信的那个版本（比如没有篡改。。），以及它跑在一个可信的环境里面（真的在encalve里面）呢？这就需要Remote
Attestation （RA），你可以查阅Intel SGX的相关文档。
Indeed true. May I create a new pull request to simplify the code?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
CI passed: http://ci.mesalock-linux.org/qinkunbao/incubator-teaclave/66
--
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/pull/349#issuecomment-650279135
Thanks @mssun and @yc-huang . The gbdt example also specifies the ownership of
the file, which is missing in the above code. Is it necessary to define the
`ownership` if it is a single user task?
OK. Thanks for the information. Could you please type `make run-tests` or `make
run-examples`
after you build the project?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Did you try other examples (e.g., builtin_gbdt_train.py)? Did they work as
expected on your machine?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
CI passed: http://ci.mesalock-linux.org/qinkunbao/incubator-teaclave/34
--
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/pull/353#issuecomment-643546813
## Description
Add a simple PSI implementation.
CI passed: http://ci.mesalock-linux.org/qinkunbao/incubator-teaclave/28/2/5
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking
Closed #352.
--
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/pull/352#event-3435741670
CI passed: https://ci.mesalock-linux.org/qinkunbao/incubator-teaclave/15
--
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/pull/352#issuecomment-642866085
#127 Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature
Thanks for your help!
--
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/pull/345#issuecomment-642325363
## Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature
## Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature
Closed #343.
--
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/pull/343#event-3423037748
The minimum supported Ubuntu version of the SDK is 16.04. And I believe the
default version of GCC for Ubuntu 16.04 should completely support C99. Is that
right?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
## Description
The previous implementation may output incorrect auth_tag values. I tested the
current implementation with several files, including an end-to-end example
(PSI).
## Type of change (select or add applied and delete the others)
- [x] Bug fix (non-breaking change which fixes an
## Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature
## Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature
Closed #337.
--
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/pull/337#event-3409800184
PSI will be a separate PR.
## Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an
Thank you for the feedback. All requested changes are addressed now.
--
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/pull/325#issuecomment-637254576
OK, I added this example and all tests passed.
--
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/pull/325#issuecomment-636814802
## Description
Add a built-in function.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would
## Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature
71 matches
Mail list logo
