Hi @Agzs, sorry for the late reply. I am still trying to figure out your
issues. Since I cannot reproduce the problem you have, can you provide some
logs of the services when executing the function by set the env var to
`TEACLAVE_LOG=debug`?
--
You are receiving this because you are subscribed
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:
https://github.com/apache/incubator-teaclave-sgx
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
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
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
(https://t
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 license
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 SDK
> 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
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 misu
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 y
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 re
> 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 errors
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.
Re
## Description
Add permlink for codebase's 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 codebase's README
-- File Changes --
M binder/README.md (4)
M cry
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
- 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: is_x86_featur
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
- 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 #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
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:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/281#issu
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
## 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 docs/R
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
GI
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 thread.
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
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
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
## Description
[Veracruz](https://github.com/veracruz-project/veracruz) is a framework for
defining and deploying collaborative, privacy-preserving computations amongst a
group of mutually mistrusting individuals.
Veracruz is using Teaclave SGX SDK to build up the framework and going to join
t
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
设置 `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 #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
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
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 vi
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
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:
https://github.com/apache/incubator-teaclave/pull/438#issuecomment-73
## 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 Su
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
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
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
## 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 --
https://github.c
Merged #440 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/440#event-4091280301
## Description
This will also be included in the generated homepage.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/441
-- Commit Summary --
* Add instruction to report security issue in the community page
-- File Changes -
Merged #441 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/441#event-4102653968
Yes, we already have the `SECURITY.md` file.
- https://github.com/apache/incubator-teaclave/blob/master/SECURITY.md
- https://github.com/apache/incubator-teaclave/security/policy
I also add this to the `COMMUNITY.md` file to make sure people from the
homepage can see it. Now, it's online:
http
Add instructions to report security issues.
This file will also be shown as the security policy in the
"Security" section in GitHub.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave-sgx-sdk/pull/297
-- Commit Summary --
* Add ins
Merged #297 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/297#event-4103434447
Merged #442 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/442#event-4103622715
你的 submodule 没有 commit？
--
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/443#issuecomment-745560980
请问你是如何启动 teaclave services 的？
--
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/444#issuecomment-745693959
明白了，这里应该是 execution service 的 docker 无法访问 localhost 这个文件系统才出现的错误。
--
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/444#issuecomment-745704173
一个解决方法是修改 docker compose 文件：
```patch
diff --git a/docker/docker-compose-ubuntu-1804-sgx-sim-mode.yml
b/docker/docker-compose-ubuntu-1804-sgx-sim-mode.yml
index aa5388d..b0f25aa 100644
--- a/docker/docker-compose-ubuntu-1804-sgx-sim-mode.yml
+++ b/docker/docker-compose-ubuntu-1804-sgx-sim-mode.yml
> wget http://docker_teaclave-file-service_1:6789
--2020-12-16 10:22:58-- http://docker_teaclave-file-service_1:6789/
Resolving docker_teaclave-file-service_1 (docker_teaclave-file-service_1)...
failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘docker_teaclave-fil
感觉没问题，你能确认一下 pull 下来的 crates-io 的 submodule 是你新的地址么 (https://xxx/crates-io)？
--
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/443#issuecomment-746761441
加密文件通过 Teaclave Command Line Tool 得到:
https://github.com/apache/incubator-teaclave/tree/master/cli
--
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/445#issuecomment-74676279
## Description
This can help people to run examples with registered input files.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/446
-- Commit Summary --
* Add a teaclave-file-service container to the docker compose file to h
This can fix #444, which new user may encounter.
--
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/446#issuecomment-747150495
## Description
- Add a builtin function called `builtin-password-check`.
- A corresponding example is also added.
The purpose of this function is to demonstrate a usage scenario of Teaclave on
threat intelligence.
You can view, comment on, or merge this pull request online at:
https://github
CI passed: http://ci.mesalock-linux.org/mssun/incubator-mesatee/1103
--
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/447#issuecomment-747187329
Merged #446 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/446#event-4130928811
Merged #447 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/447#event-4131080717
Closed #444.
--
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/444#event-4131565360
1. mesatee是使用mesapy来支持矩阵操作的吗？
MesaPy 作为 Teaclave 的一个 executor，可以执行 Python function。同时还可以使用 native
executor，也就是用 Rust 编写 builtin function。两种 executor 均可以支持矩阵操作。
2. 现在mesapy支不支持pandas做一些矩阵（表）操作？
现在不支持 import pandas。
MesaPy 提供了 Python 2 的 builtin types 和 builtin functions 以及一些基本的
modules。关于问题中的矩
oped 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.
有一下几个原因：
- SGX EPC 大小受限，多线程不会带来太多的 performance gain
- 线程之间没有内存隔离（进程隔离），不同 task 在同一进程执行可能会带来安全隐患
一台物理机启动多个 execution-service 的方式进行并发执行应该能满足现在的需求。
--
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/incu
@gaojunjie03 多谢你的回答，非常准确。现在文档还不是很完善，阅读代码会更直接一些。
--
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/450#issuecomment-754297890
Closed #450.
--
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/450#event-4171538429
"std Aware Cargo" (https://github.com/rust-lang/wg-cargo-std-aware) is one of
the most important building blocks for Teaclave SGX SDK. With this, we can
build SGX enclave without worry about the complexity brought by Xargo or no-std
Cargo. However this is a long-term plan for Cargo, which doesn'
Hi Dave,
Thanks for the reminder. Don't know why I missed this email.
To mentors, I will prepare the report today.
Best,
Mingshen
On Wed, Jan 6, 2021 at 10:44 AM Dave Fisher wrote:
>
> A reminder to discuss and submit a report.
>
> Thanks,
> Dave
>
> On 2020/12/24 00:35:06, jmcl...@apache.org
Jan 6, 2021 at 10:48 AM Mingshen Sun wrote:
>
> Hi Dave,
>
> Thanks for the reminder. Don't know why I missed this email.
>
> To mentors, I will prepare the report today.
>
> Best,
> Mingshen
>
> On Wed, Jan 6, 2021 at 10:44 AM Dave Fisher wrote:
> &g
- Matt Sicker
Non binding vote:
- Gao,Yingchun
Thank you all. I will work to complete the donation process.
On Tue, Jan 5, 2021 at 8:02 PM Mingshen Sun wrote:
>
> Thanks Matt. Yes, the software grant will be submitted once the voting is
> done.
>
> On Tue, Jan 5, 2021 at 8:00 PM Mat
- SPID, KEY 是给 Intel Attestation Service [1] 使用的。
- 除了用 Intel Attestation Service，也可以用 DCAP [2] 搭建 offline 的 attestation。
[1] https://api.portal.trustedservices.intel.com/EPID-attestation
[2] https://teaclave.apache.org/docs/codebase/dcap/
--
You are receiving this because you are subscribed to
Hi community,
The incubating projects are also eligible for the GSoC.
If you are eligible students for GSoC
(https://summerofcode.withgoogle.com/get-started/) and want to
contribute to Apache Teaclave (incubating). Please feel free to
contact the community. I'm more than happy to help you.
For m
## Description
Add Rust client SDK.
## 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 cause existing functional
a detailed schedule and link for the meetup (e.g., Zoom).
Feel free to reply if you have any suggestion for the meetup. Thanks.
--
Best,
Mingshen Sun
I'll add doc comments later when the APIs becomes table.
--
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/455#issuecomment-762556684
Merged #455 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/455#event-4220892931
## Description
`build.rs` is not used right now.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/456
-- Commit Summary --
* Remove unnecesary build.rs
-- File Changes --
D sdk/rust/build.rs (20)
-- Patch Links --
http
Merged #456 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/456#event-4224045807
Merged #457 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/457#event-4224127514
Last year, we published an RFC - "Roadmap: Towards the First Public Release"
[1]. Thanks for the continuous efforts made by the community. We have completed
several milestones and amazing achievements.
Specifically, we published the first Apache incubator release - version 0.1.0
[2]. In this re
For DCAP, `AS_ALGO` is `ecdsa`. `AS_URL` is the URL of your data center
attestation service. `AS_KEY` and `AS_SPID` are not used for DCAP.
--
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-t
This link
(https://software.intel.com/content/www/us/en/develop/articles/intel-software-guard-extensions-data-center-attestation-primitives-quick-install-guide.html)
contains a lot useful documents.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directl
Thanks for your proposal. Sorry for the late reply. Can you provide a simple
example to clarify your goal. More specifically, I'd like to see what kind of
outputs you will contribute (e.g., formal document, proof, and readme to
reproduce). Please try your best to list them. The followup question
1. 我们暂时没有相关，主要的学习资料还是来自 Intel 官方文档。
2. 需要重新编译（https://teaclave.apache.org/docs/codebase/dcap/）：
> By default, Intel Attestation Service (IAS) will be used for attestation in
> Teaclave. To use DCAP instead of IAS, you have to first build Teaclave with
> DCAP enabled (by appending -DDCAP=ON optio
Thanks for your request. I have added it in our 2021 plan (#460).
--
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/449#issuecomment-763382200
Ok, yours is different. The `docker-compose` reports an error. There are
something wrong with the `docker-compose-ubuntu-1804-sgx-sim-mode.yml` file.
Here is a patch. I'll create a PR to solve this issue. Thanks.
```diff
diff --git a/docker/docker-compose-ubuntu-1804-sgx-sim-mode.yml
b/docker/d
## Description
Make container names consistent.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/462
-- Commit Summary --
* Fix sim mode docker compose file
-- File Changes --
M docker/docker-compose-ubuntu-1804-sgx-sim-
See PR #462.
--
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/461#issuecomment-763428079
1. I saw that several services have exited.
2. You should install the `toml` module.
--
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/463#issuecomment-763823660
## Description
People may forget to install the Python modules when directly read the step by
step instruction in the doc.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/464
-- Commit Summary --
* Improve the step by step i
Merged #462 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/462#event-4229568352
Merged #464 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/464#event-4229569715
Thanks for reporting this. No, this is not caused by the needs of new crates.
This is because all of our dependencies for the frameworks, SDKs, cli, etc. are
vendored for offline building. However, this is managed by the build system
(i.e., cmake). If you want to compile a crate directly in side
## Description
Fix #465.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/467
-- Commit Summary --
* Don't use offline to build the proto when not within Teaclave's
build system
-- File Changes --
M services/proto/build
Merged #467 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/467#event-4236312451
Closed #465 via #467.
--
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/465#event-4236312457
up. Thanks!
Best,
Mingshen
On Mon, Jan 18, 2021 at 5:51 PM Mingshen Sun wrote:
> Dear Teaclave community,
>
> Last year, we organized several private offline meetups with our core
> contributors. This gave us a good chance to discuss the project.
>
> In the year of 2021, I pla
l update to the wiki later [1]. Thank you so
much!
[1] https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list
Best,
Mingshen Sun
On Fri, Jan 15, 2021 at 5:30 PM Mingshen Sun wrote:
> Hi community,
>
> The incubating projects are also eligible for the GSoC.
>
> If
## Description
Introduce C client SDK. There are two types of C APIs:
- `*_serialized` APIs accept JSON serialized string requests and responses.
These APIs is for other high level programming languages.
- Normal APIs like `teaclave_user_login`.
An echo example using C client SDK is also impleme
Thanks for the review! Merged.
--
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/470#issuecomment-767745980
501 - 600 of 1057 matches
Mail list logo
