[apache/incubator-teaclave] Be stuck with registering input file when writing builtin-gbdt-train python script (#314)
Hi, I'm writing builtin-gbdt-train python sample script. I got a problem about rewrite the registering input and output files. I imitated the code like register_function like making a RegisterInputFileRequest class and so on, but I invalid request error. Here is my code: def register_input_file(self): url = "http://localhost:6789/fixtures/functions/gbdt_training/train.enc"; cmac = "881adca6b0524472da0a9d0bb02b9af9" crypto_info = "" request = RegisterInputFileRequest(self.metadata, urlparse(url), FileAuthTag(cmac), TeaclaveFile128Key(crypto_info)) write_message(self.channel, request) response = read_message(self.channel) return reponse["content"]["data_id"] -- 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/314
Re: [apache/incubator-teaclave] Be stuck with registering input file when writing builtin-gbdt-train python script (#314)
Hi, thanks! You can enable the log with `RUST_LOG=debug=teaclave` to check the request format is a valid or not by comparing to the Rust's test. -- 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/314#issuecomment-633690769
[apache/incubator-teaclave] Polish and improve documentation (#315)
## Description - Polish and improve documentation - Add document for built-in functions You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave/pull/315 -- Commit Summary -- * Add docs for built-in functions * Update README.md * Update docs * Update contributors * Update README.md * Update third_party README.md -- File Changes -- M CONTRIBUTORS.md (56) M README.md (8) M config/README.md (4) M executor/README.md (5) A function/README.md (23) M services/README.md (15) M tests/README.md (6) M third_party/README.md (40) -- Patch Links -- https://github.com/apache/incubator-teaclave/pull/315.patch https://github.com/apache/incubator-teaclave/pull/315.diff -- 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/315
Re: [apache/incubator-teaclave] Polish and improve documentation (#315)
Fixed. -- 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/315#issuecomment-633741520
Re: [apache/incubator-teaclave] Polish and improve documentation (#315)
Merged #315 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/315#event-3371439413
Re: Teaclave Website
Site's looking pretty nice so far! On Sun, 24 May 2020 at 16:30, Furkan KAMACI wrote: > > Hi Mingshen, > > Thanks for initiating this! > > Kind Regards, > Furkan KAMACI > > On Mon, May 25, 2020 at 12:18 AM Mingshen Sun wrote: > > > Hi, I just added the blog feature in our website: > > https://teaclave.apache.org/blog/ > > > > Right now, only previous podling reports are posted. Later, we can add > > more articles such as release note, background knowledge, design > > choice, case studies, and community activities. Thanks! > > > > On Sat, May 16, 2020 at 12:24 PM Felix Cheung > > wrote: > > > > > > Great! > > > > > > > > > From: Mingshen Sun > > > Sent: Friday, May 15, 2020 6:44:48 PM > > > To: dev@teaclave.apache.org > > > Subject: Re: Teaclave Website > > > > > > Thank you. I've also added community and contributors pages to the > > website. > > > > > > On Fri, May 15, 2020 at 6:18 PM Furkan KAMACI > > wrote: > > > > > > > > Hi, > > > > > > > > Thanks for your effort on the website! I see that the ASF Sponsorship > > URL > > > > is not right. So, I've created a PR for it. > > > > > > > > Kind Regards, > > > > Furkan KAMACI > > > > > > > > > > > > > > > > On Sat, May 16, 2020 at 1:35 AM Felix Cheung < > > felixcheun...@hotmail.com> > > > > wrote: > > > > > > > > > This is great - you might want to add links to mail archive (dev@) > > and a > > > > > page on the community (people) > > > > > > > > > > > > https://incubator.apache.org/guides/sites.html#creating_a_good_podling_site > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: Mingshen Sun > > > > > Sent: Thursday, May 14, 2020 5:55:35 PM > > > > > To: dev@teaclave.apache.org > > > > > Subject: Re: Teaclave Website > > > > > > > > > > Hi folks, > > > > > > > > > > I have setup a website for Teaclave: https://teaclave.apache.org/ > > > > > > > > > > Currently, the site generator can automatically fetch docs from our > > > > > main repository. The source code can be found here: > > > > > https://github.com/apache/incubator-teaclave-website/. > > > > > > > > > > I'll include more information in this website. Feel free to comment > > > > > and help me to improve the website. Thanks. > > > > > > > > > > > > > > > On Wed, May 13, 2020 at 6:39 PM Furkan KAMACI < > > furkankam...@gmail.com> > > > > > wrote: > > > > > > > > > > > > Hi Mingshen, > > > > > > > > > > > > Great! > > > > > > > > > > > > Kind Regards, > > > > > > Furkan KAMACI > > > > > > > > > > > > On Thu, May 14, 2020 at 4:38 AM Mingshen Sun > > wrote: > > > > > > > > > > > > > Great, I can access this repo now. It takes about 1h to > > propagate the > > > > > rule. > > > > > > > > > > > > > > On Wed, May 13, 2020 at 6:19 PM Mingshen Sun > > wrote: > > > > > > > > > > > > > > > > I have created a new repo (apache/incubator-teaclave-website) > > for > > > > > > > > hosting sources and pages here [1]. > > > > > > > > > > > > > > > > It appears in GitHub immediately > > > > > > > > (https://github.com/apache/incubator-teaclave-website). > > However, I > > > > > > > > don't have access to this repo now. I'm not sure whether it > > takes > > > > > some > > > > > > > > time to propagate the access control rule to GitHub or I need > > to > > > > > > > > submit a ticket to INFRA for help. > > > > > > > > > > > > > > > > [1] https://gitbox.apache.org/setup/newrepo.html. > > > > > > > > > > > > > > > > On Wed, May 13, 2020 at 3:45 PM Furkan KAMACI < > > > > > furkankam...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi Mingshen, > > > > > > > > > > > > > > > > > > Sure! Feel free to ask if you have any questions. > > > > > > > > > > > > > > > > > > Kind Regards, > > > > > > > > > Furkan KAMACI > > > > > > > > > > > > > > > > > > On Thu, May 14, 2020 at 1:04 AM Mingshen Sun < > > ms...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > > > > Thanks for asking, Furkan. > > > > > > > > > > > > > > > > > > > > I did some research on how to deploy a website under the > > Apache > > > > > > > > > > infrastructure. There are several options > > > > > > > > > > (https://infra.apache.org/project-site.html). Since we are > > > > > mainly > > > > > > > > > > working on GitHub, I think the GitHub pages fit our needs. > > We > > > > > can use > > > > > > > > > > .asf.yml to configure the deployment > > > > > > > > > > ( > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories > > > > > > > > > > ). > > > > > > > > > > > > > > > > > > > > Let me try to start with a simple one with essential > > information > > > > > and > > > > > > > > > > later polishing details. > > > > > > > > > > > > > > > > > > > > On Wed, May 13, 2020 at 9:55 AM Furkan KAMACI < > > > > > > > furkankam...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > > > As far as I k
Re: [apache/incubator-teaclave-sgx-sdk] v1.1.2: `InternalBacktrace` in the backtrace feature of tstd (#238)
I was able port this crate, at least according to my needs. -- 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/238#issuecomment-633793786
Re: [apache/incubator-teaclave-sgx-sdk] v1.1.2: `InternalBacktrace` in the backtrace feature of tstd (#238)
Closed #238. -- 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/238#event-3371781087
[apache/incubator-teaclave-sgx-sdk] TLS -> TCS policy must be bound (#240)
I recently upgraded to sdk 1.1.2, and I'm getting this error with a TLS client
similar to the example provided.
```
thread '' panicked at 'Can not access a Thread Local Storage value:
AccessError { msg: "If TLS data needs to be destructed, TCS policy must be
Bound." }',
/root/.cargo/git/checkouts/teaclave-sgx-sdk-be25c2ad2f03718d/253b3ac/sgx_tstd/src/thread/local.rs:148:9
note: Call backtrace::enable_backtrace with 'PrintFormat::Short/Full' for a
backtrace.
fatal runtime error: failed to initiate panic, error 5
``
Any clues on how to investigate would be appreciated.
--
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/240
Re: [apache/incubator-teaclave-sgx-sdk] TLS -> TCS policy must be bound (#240)
Please configure Enclave.config.xml > TCSPolicy TCS management policy. 0 – TCS is bound to the untrusted thread. 1 – TCS is not bound to the untrusted thread. https://download.01.org/intel-sgx/linux-2.2/docs/Intel_SGX_Developer_Reference_Linux_2.2_Open_Source.pdf -- 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/240#issuecomment-633805976
Re: [apache/incubator-teaclave-sgx-sdk] TLS -> TCS policy must be bound (#240)
> I recently upgraded to sdk 1.1.2, and I'm getting this error with a TLS
> client similar to the example provided.
>
> ```
> thread '' panicked at 'Can not access a Thread Local Storage value:
> AccessError { msg: "If TLS data needs to be destructed, TCS policy must be
> Bound." }',
> /root/.cargo/git/checkouts/teaclave-sgx-sdk-be25c2ad2f03718d/253b3ac/sgx_tstd/src/thread/local.rs:148:9
> note: Call backtrace::enable_backtrace with 'PrintFormat::Short/Full' for a
> backtrace.
> fatal runtime error: failed to initiate panic, error 5
> ```
>
> Any clues on how to investigate would be appreciated.
The reason is that something is relying on thread local storage, while your
enclave is configured as `TCSPOLICY = UNBOUND` which means your enclave does
not support thread local storage.
The most frequent case is using `rand::thread_rng`, which depends on thread
local storage.
--
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/240#issuecomment-633824518
Re: [apache/incubator-teaclave-sgx-sdk] TLS -> TCS policy must be bound (#240)
When `TCSPOLICY = UNBOUND`, each root ECALL will re-initialize thread local storage, so in most cases, when using thread local storage, you should configure the enclave TCS policy to bound. -- 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/240#issuecomment-633832339
