## Description
Typo in the mailing list.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/440
-- Commit Summary --
* Fix typo in the mailing list
-- File Changes --
M COMMUNITY.md (2)
-- Patch Links --
Can you confirm the `teaclave_frontend_service` file is successfully generated?
--
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/437#issuecomment-740248126
Merged #438 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/pull/438#event-4082161794
Merged #439 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/pull/439#event-4081038604
## Description
Add recent new contributors (including both Teaclave SGX SDK and Teaclave
projects) to the list.
This will be updated to the homepage once merged.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/439
-- Commit
There are conflicts of your branch. Please rebase your change to the latest
upstream master first. Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I see "signal: 9, SIGKILL: kill" in your log. I believe this is cause by the
out of memory, resulting compilation failed. Please increase your memory if
your are using VM in cloud service or docker in Mac.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
The `teaclave_frontend_service` is the output of compilation. Seems that your
building was failed. Can you check if there are service binaries generated in
the `release/services/` direactory?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
Nice catch! 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/pull/436#issuecomment-737595466
Merged #436 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/pull/436#event-4065087557
设置 `Enclave.config.xml` 文件中的 `StackMaxSize` 可以调整 SGX enclave 的 stack size。
--
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/435#issuecomment-729271093
Merged #433 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/pull/433#event-3991186210
Closed #277.
--
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/277#event-3987208453
I found that file mode is changed from 100644 → 100755.
--
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/284#issuecomment-725873630
Merged #432 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/pull/432#event-3968421018
You can implement you own executor.
I don't understand your question. I guess you were asking how to add your
executor into the Teaclave execution service. Yes, you can refer to the
interfaces of MesaPy and Builtin executors.
--
You are receiving this because you are subscribed to this
Add a subcommand of `teaclave_cli`.
Here is an example of the usage.
```
$ ./teaclave_cli attest --address accvm-dev:7776 --as-ca-cert
../../keys/ias_root_ca_cert.pem
Report Freshness: 1854s
SGX Quote status: SwHardeningNeeded
Version and signature/key type: Version 2, EPID Linkable signature
## Description
- Polish highlights
- Add notes for building with Docker for Mac
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/431
-- Commit Summary --
* Polish document
-- File Changes --
M README.md (10)
M
Closed #281.
--
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/281#event-3951437701
This is answer here:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/239#issuecomment-720773397
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Merged #429 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/pull/429#event-3949455796
- Add document
- Split docker-compose files into three for `isgx` driver, `intel_sgx` driver
and simulation mode.
- Polish the My First Function document
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/429
-- Commit Summary --
Merged #280 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/280#event-3929237479
- Developing with Visual Studio Code
- `is_x86_feature_detected` in Teaclave SGX SDK
This PR is related with #276.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave-sgx-sdk/pull/280
-- Commit Summary --
* Add document:
Merged #428 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/pull/428#event-3928029488
## Description
Add permlink for codebases README.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/428
-- Commit Summary --
* [docs] Add permlink for codebases README
-- File Changes --
M binder/README.md (4)
M
Thanks for your suggestion. We will definitely document it when we find out a
good workflow for working on third-party SGX crates. Before this, you have to
understand our build system in order to include more SGX libraries.
--
You are receiving this because you are subscribed to this thread.
> Then I guess the current version of SQLite port won't leave enclave during
> execution (since I make it support in-memory database only and it currently
> does not introduce any additional ocalls)?
Yes. Your workaround is to give some non-functional stubs. This will still
cause runtime
I put this wiki page
(https://github.com/apache/incubator-teaclave-sgx-sdk/wiki/Mitigation-of-Intel-SA-00219-in-Rust-SGX)
to our blog
(https://teaclave.staged.apache.org/blog/2019-12-02-mitigation-of-intel-sa-00219-in-teaclave-sgx-sdk/).
It's more like a blog post than document.
--
You are
In short, you cannot use third-party Rust crates which are not in the
`third_party/crates-sgx` directory.
For your case, if you want to use ndarray, you need to vendor ndarray-sgx
(https://github.com/mesalock-linux/ndarray-sgx) in the `crates-sgx` directory.
--
You are receiving this because
Sorry, it seems that my reply brings you more questions.
> But Enclave written in C is not taking advantage of rigorous checking of Rust
> sgx_tstd but instead relies on Intel's tlibc (and Intel does not provide
> checks on the primitive ocalls? I believe they also do?)
I think there's one
> But I do think by limiting the enclave programming language to Rust, and not
> trusting any external battlefield-tested library (sqlite in this case) would
> limit the scope of this project.
Yes, I agree with you. This is another topic we can discuss more.
Originally, the SGX SDK is designed
I found that you introduce some headers, what's the purpose? They are in LGPL
license which are not accepted [1] by the Apache projects.
[1] https://www.apache.org/legal/resolved.html
I don't think this can be included in Teaclave SGX SDK as samples.
- The purpose of samples in Teaclave SGX
As an Apache incubator project, we need a complete license review. According to
https://www.apache.org/legal/resolved.html, GPL/LGPL licenses are not accepted.
I found that these C headers are in the LGPL license. We need to replace them
to BSD libc header (BSD license) or musl libc (MIT
As described in #275, please help me with the documentation of SGX SDK:
- Move existing wiki into the `/documents/` directory
- Write tutorial and tips of using SGX SDK to build SGX application
- Cleanup the `/documents/` directory
This documents will be rendered in our homepage
Merged #275 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/275#event-3911631082
I'll post a call for contribution to help me migrate old wiki/documents and
write new 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/pull/275#issuecomment-714835330
I suggest to use `/documents/` directory for all SDK documentation. This will
be automatically rendered in the homepage.
See https://teaclave.apache.org/sgx-sdk-docs/ for reference.
You can view, comment on, or merge this pull request online at:
Merged #426 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/pull/426#event-3910949920
## Description
Add new committers.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/426
-- Commit Summary --
* Add new committers
-- File Changes --
M CONTRIBUTORS.md (1)
-- Patch Links --
Hi community,
Let's welcome Ran Duan to join Teaclave as a committer.
He has contributed a lot to the Teaclave SGX SDK repository for years.
Right now, he is working on our next release.
Best,
Mingshen
-
To unsubscribe,
Hi, I found that you introduce some ocalls to help your porting:
```
void ocall_print_error([in, string] const char *str);
void ocall_print_string([in, string] const char *str);
void ocall_println_string([in, string] const char *str);
int ocall_lstat([in, string]
Merged #424 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/pull/424#event-3887780030
Looks good to me. I think this can be documented somewhere so that other people
may also interested.
@dingelish, what do you think.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I have updated your PR to fix the above mentioned issues.
--
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/424#issuecomment-710401311
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/272#issuecomment-710388994
There's some warning introduces by previous PR. I don't know why they're not
linked. You can ignore them first. Like this:
```
error: unsafe function's docs miss `# Safety` section
--> binder/src/binder.rs:80:5
|
80 | / pub unsafe fn destroy() {
81 | | let _ =
Can you run `make CLP=1` to check the code? I see some warnings. Please also
fix it. 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/pull/424#issuecomment-709751350
You can start more execution services, that is to say, providing more function
workers.
--
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/425#issuecomment-708147647
Sure, I’ll update the report.
On Sat, Oct 10, 2020 at 9:18 AM Matt Sicker wrote:
> Could be updated now to reflect the status of the release.
>
> On Wed, Oct 7, 2020 at 17:55 Mingshen Sun wrote:
>
> > Hi all,
> >
> > Since the last report, we have mainl
/apache/incubator-teaclave/issues)
- Twitter (https://twitter.com/ApacheTeaclave)
Best regards,
Apache Teaclave (incubating) Team
--
Mingshen Sun
This is the first Apache Incubator release of Teaclave. Apache Teaclave
(incubating) is an open source ***universal secure computing***
platform, making computation on privacy-sensitive data safe and simple.
Apache Teaclave (incubating) has following highlights:
- **Security**: Teaclave adopts
. (PODLINGNAMESEARCH-175)
On Sat, Sep 19, 2020 at 6:13 PM Mingshen Sun wrote:
> Hi all,
>
> I'll prepare the report in these days. Thanks.
>
> Best,
> Mingshen
>
> On Sat, Sep 19, 2020 at 6:07 PM wrote:
>
>> Dear podling,
>>
>> This email was sent b
Merged #423 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/pull/423#event-3822661620
hat you can also reply with things you have checked.
Best,
Mingshen Sun
This is the first Apache Incubator release of Teaclave. Apache Teaclave
(incubating) is an open source ***universal secure computing***
platform, making computation on privacy-sensitive data safe and simple.
Apache Teaclave (incubating) has following highlights:
- **Security**: Teaclave adopts
Merged #422 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/pull/422#event-3822027555
## Description
Fix building issue when source is not in the git repo.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/422
-- Commit Summary --
* Fix building issue when source is not in the git repo
-- File Changes --
ample in
> simulation mode.
>
> Best,
> Tongxin Li
>
> On Tue, Sep 22, 2020 at 8:00 PM Mingshen Sun wrote:
>
> > Dear Teaclave community,
> >
> > I am pleased to be calling this vote for the first release of Apache
> > Teaclave (incubating) 0.1.0 (
:
-
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
Since this voting is the first time for the Teaclave community, I'd like to
mention that you can also reply with things you have checked.
Best,
Mingshen Sun
This is the first Apache Incubator release of Teaclave. Apache Teaclave
(incubating) is an open source ***universal secure computing***
platform, making computation on privacy-sensitive data safe and simple.
Apache Teaclave (incubating) has following highlights:
- **Security**:
Teaclave
Hi all,
I'll prepare the report in these days. Thanks.
Best,
Mingshen
On Sat, Sep 19, 2020 at 6:07 PM wrote:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly
Please change the pre-defined heap size in the `Enclave.config.xml` files. You
can find it in each service's enclave directory. (e.g.,
`services/execution/enclave/Enclave.config.xml`)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
Can you set the env var `export TEACLAVE_LOG=debug` before running the tool as
well?
--
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/411#issuecomment-689307413
Merged #418 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/pull/418#event-3743311352
Hi, in this PR #416, I have fixed the issue about error message printing. Can
you pull the latest master and compile the teaclave sgx tool again? Then, you
will get the error message in the standard output. Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to
Merged #417 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/pull/417#event-3743238880
Merged #416 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/pull/416#event-3743238028
Merged #415 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/pull/415#event-3725898158
## Description
- Add an option to the build system: use `USE_PREBUILT_MESAPY` to config
whether to use the prebuilt library.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/415
-- Commit Summary --
* Use USE_PREBUILT_MESAPY
## Description
In this MesaPy version, we updated the exec enclave and add `gc.collect()`
after a function eval.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/414
-- Commit Summary --
* Update MesaPy to
## Description
When receiving singals like SIGTERM, SIGINT, the services will be terminated
immediately. Before exiting the process, we force to call enclave destroy. This
will help us to collect sgx_emmt information if needed.
Also, two global variables are added for profiling memory usage.
Merged #408 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/pull/408#event-3705087698
Thanks for the report. Can you print the TLS extension here
https://github.com/apache/incubator-teaclave/blob/47b8573df074ac1879aa082e5ea23d8d5baaee9d/sdk/python/teaclave.py#L459.
Seems that the sigining certification you got from the attestation report is
invalid.
--
You are receiving this
Since there is no update on this issue, I'm closing it. Feel free to reopen if
you think it's still valid. Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #404.
--
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/404#event-3692041950
## Description
Use `DISCLAIMER-WIP` to disclaim potential issues.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/409
-- Commit Summary --
* Use DISCLAIMER-WIP
-- File Changes --
D DISCLAIMER (8)
A DISCLAIMER-WIP
release. Thanks.
Best,
Mingshen Sun
- [1] https://github.com/apache/incubator-teaclave/issues/121
## Description
- Add license header to *.sh and *.py and change version number to 0.1.0
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/408
-- Commit Summary --
* Versions changed to 0.1.0
* Add license header
-- File
Closed #121.
--
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/121#event-3681237164
Hi all, we follow this roadmap and finish most of the refactoring and features.
I'm closing this issue and plan to initiate and official Apache incubator
release. Thanks for all contributors.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
Hi @hoshinoko, any update?
--
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/404#issuecomment-678496073
Merged #407 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/pull/407#event-3664061400
## Description
- Add my public key to KEYS for release code signing.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/407
-- Commit Summary --
* Add KEYS for code signing
-- File Changes --
A KEYS (70)
-- Patch Links
Sorry, we do not support the libraries you mentioned for data analytics.
However, you can write you own function to achieve similar functionalities.
BTW, Apache Arrow's Rust implementation looks promising [1]. I hope someone may
help and find out if it works for Teaclave.
- [1]
Merged #406 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/pull/406#event-3663562527
## Description
Add an instruction to report security issues.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/406
-- Commit Summary --
* Add instruction to report security issue
-- File Changes --
A SECURITY.md (8)
--
I'm closing this issue. Will create a new one if we are ready for organizing an
online meetup. Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #122.
--
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/122#event-3649477870
Thanks for your report.
For CLI, the key is in hex format, while in Python SDK, key is in binary array.
`1234` should be `[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0x12, 0x34]`.
--
You are receiving this because you are subscribed to this thread.
Reply to this
Any update on this issue?
--
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/403#issuecomment-671687297
I have listed some projects and organizations using Teaclave here:
http://teaclave.apache.org/community/#organizations-and-projects. I'm closing
this issue. If you want to add your project/organization in this list, feel
free to ask in our mailing list. Thanks.
--
You are receiving this
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/issues/310#event-3640446263
Closed #374.
--
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/374#event-3640439690
Since there's no more question, I'm closing this issue.
--
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/374#issuecomment-671582871
There are two places which may report this error:
```
config
.root_store
.add_pem_file( DCAP_ROOT_CA_CERT.to_string().as_bytes())
.map_err(|_| AttestationServiceError::TlsError)?;
```
and
```
let mut stream = new_tls_stream(url).map_err(|_|
@yc-huang what did you mean? The `try_from` function will deserialize
`FaceDetectionArguments` based on its fields automatically. No need to change
this function.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
## Description
- Use byte array instead of base64
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/402
-- Commit Summary --
* Use byte array instead of base64 for image transfer making parsing faster
-- File Changes --
Hi, thanks for asking. This is one of our limitation for the MesaPy executor.
One way to debug Python scripts is to directly use the standalone MesaPy for
SGX. For instance, you can use the exec example
(https://github.com/mesalock-linux/mesapy/tree/sgx/sgx/examples/exec) to
develop the Python
Closed #400.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/400#event-3623120195
501 - 600 of 987 matches
Mail list logo
