Re: [apache/incubator-teaclave-sgx-sdk] Sqlite3 Port (#274)

2020-10-23 Thread Rd
> 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 > They are system headers. The common/inc folder misses some of the definitions. They could be trimmed

Re: [apache/incubator-teaclave-sgx-sdk] Sqlite3 Port (#274)

2020-10-23 Thread Rd
Closed #274. -- 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/274#event-3913760034

[GitHub] [incubator-teaclave-website] qinkunbao opened a new pull request #2: Update 2020-10-22-announcing-teaclave-0.1.0.md

2020-10-23 Thread GitBox
qinkunbao opened a new pull request #2: URL: https://github.com/apache/incubator-teaclave-website/pull/2 Fix some typos. This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

Re: [apache/incubator-teaclave-sgx-sdk] Sqlite3 Port (#274)

2020-10-23 Thread Mingshen Sun
> 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

Re: [apache/incubator-teaclave-sgx-sdk] Sqlite3 Port (#274)

2020-10-23 Thread Rd
> > 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 SD