Merged #255 into develop.
--
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/255#event-3186183225
Merged #254 into develop.
--
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/254#event-3174567170
Merged #253 into develop.
--
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/253#event-3174081952
Closed #239.
--
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/239#event-3173549984
Since this PR is stale, I'm closing it. Feel free to reopen or create a new one
if there is any update.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I think this can be closed. Feel free to reopen or create a new one if there
are some updates. Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #242.
--
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/242#event-3170874402
Merged #252 into develop.
--
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/252#event-3170873116
The subcommand interfaces:
```
teaclave_cli encrypt --algorithm teaclave_file_128 --input-file input.txt
--output-file output.enc
teaclave_cli encrypt -a teaclave_file_128 -i input.txt -o output.enc
teaclave_cli decrypt --algorithm teaclave_file_128 --input-file input.enc
--output-file
Merged #250 into develop.
--
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/250#event-3169896979
Merged #249 into develop.
--
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/249#event-3169266765
Merged #248 into develop.
--
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/248#event-3165640717
Hi folks,
I have an initial version of the report. Feel free to comment if
something is missing.
## Teaclave
Teaclave is a universal secure computing platform.
Teaclave has been incubating since 2019-08-20.
### Three most important unfinished issues to address before graduating:
1.
Merged #247 into develop.
--
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/247#event-3162278583
Merged #246 into develop.
--
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/246#event-3160840680
I agree, thank you so much! @devashishdxt
@sammyne I know you are reading the attestation part recently, can you help to
review this doc/comment for the attestation? Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Since the recent update of Intel attestation service protocol, DCAP 1.3's QVE
is no longer compatible with the new protocol. Specifically, a new TCB status
(SWHardeningNeeded) is introduced, which QVE will reject it and give an
`SGX_QL_TCBINFO_UNSUPPORTED_FORMAT` error. DCAP 1.5 has fixed this
Merged #244 into develop.
--
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/244#event-3156130472
Merged #243 into develop.
--
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/243#event-3153704322
Closed #79.
--
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/79#event-3153240518
This has been implemented in the `develop` branch, which will be merged into
`master` in the near future.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #100.
--
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/100#event-3153239620
This issue has been solved. Currently, we manually upload result to coveralls
(https://coveralls.io/github/apache/incubator-teaclave). We'll integrate with
our CI in the near future.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Merged #241 into develop.
--
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/241#event-3144196835
Merged #240 into develop.
--
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/240#event-3142709042
Thanks for the PR.
- Since I'm not sure if some of the dependencies are from the "recommended
packages", have you compiled the project with the updated docker image (which
with `--no-install-recommends` on)?
- We are working on the `develop` branch right now. If you want to make any
changes
I see. Okay, then it seems that the compilation time won't be changed.
--
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/236#issuecomment-597452652
Merged #238 into develop.
--
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/238#event-3116973199
Hi Vijay,
Thanks for your interests in the Rust OP-TEE TrustZone SDK. At this
point, I know that it is a bit confusing for other people. Let me
answer your question first and explain the rationale behind it.
For now, Rust OP-TEE TrustZone SDK is a separate project maintained by
me. Since most
Thanks, I suggest we can discuss this proposal in several aspects:
- readability
- complexity of the building system (maintenance, adding/deleting new
services, etc.)
- compilation time
I also added test in your proposal:
```
|-teaclave
|-...
|-examples // A CARGO WORKSPACE
Merged #237 into develop.
--
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/237#event-3115684168
Merged #235 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/235#event-3113254562
Closed #130.
--
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/130#event-3113232486
## Description
Update README to add links to the develop branch for the latest implementation.
Since we have branch protection on the `master` branch, this PR needs at least
one reviewer to approve.
You can view, comment on, or merge this pull request online at:
Merged #234 into develop.
--
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/234#event-3112848153
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/233#issuecomment-596621972
Merged #233 into develop.
--
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/233#event-3111326282
Merged #232 into develop.
--
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/232#event-3099423524
This is another example to trigger the segfault:
https://github.com/sammyne/rsgx-fs-playground
Basically, `std::untrusted::fs::read()` will do ocall and read a large size of
data on stack, resulting segmentation fault.
--
You are receiving this because you are subscribed to this thread.
Reply
Merged #231 into develop.
--
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/231#event-3083763582
Merged #230 into develop.
--
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/230#event-3079276337
Merged #229 into develop.
--
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/229#event-3072116809
Merged #228 into develop.
--
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/228#event-3058962820
I have updated the original post of roadmap to reflex current status in the
`develop` branch.
--
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#issuecomment-589321109
Merged #227 into develop.
--
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/227#event-3049944936
Merged #226 into develop.
--
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/226#event-3048839136
Merged #225 into develop.
--
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/225#event-3040474476
Merged #224 into develop.
--
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/224#event-3033437841
Merged #223 into develop.
--
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/223#event-3033163775
Merged #222 into develop.
--
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/222#event-3033151493
Merged #221 into develop.
--
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/221#event-3028215137
Thanks for your implementation. Currently, we are working on the `develop`
branch, and current `master` branch will be deprecated. Anyway, although we
haven't started to develop the CLI, your implementation is definitely useful
for our new version.
BTW, I have updated the `structopt` to 0.3.9
Merged #220 into develop.
--
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/220#event-3024360661
Merged #219 into develop.
--
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/219#event-3015939670
Merged #218 into develop.
--
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/218#event-3011945332
Merged #217 into develop.
--
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/217#event-3008740826
Merged #216 into develop.
--
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/216#event-3008055792
Merged #215 into develop.
--
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/215#event-3004938544
Merged #213 into develop.
--
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/213#event-2995132823
Merged #212 into develop.
--
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/212#event-2992295547
Merged #211 into develop.
--
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/211#event-2992025706
Merged #210 into develop.
--
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/210#event-2990719164
Merged #209 into develop.
--
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/209#event-2983706407
Since we are working on the `develop` branch, 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/140#issuecomment-578595769
Closed #140.
--
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/140#event-2980539922
Closed #103.
--
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/103#event-2980197892
Closed. Completed in the `develop` branch.
--
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/103#issuecomment-578547275
mailing list commands,
> though it also offers some sort of mail client to send the command for
> you. I tried adding notificati...@github.com by sending a message to
> dev-allow-subscribe-notifications=github@teaclave.apache.org
> though that doesn't seem to have done the trick.
>
l address. Let's see if the next GitHub
> notification makes it through.
>
> On Thu, 16 Jan 2020 at 23:51, Mingshen Sun wrote:
> >
> > Ok, let me check with the INFRA team to see what's wrong.
> >
> > On Thu, Jan 16, 2020 at 9:49 PM Matt Sicker wrote:
> > >
&g
etting up GH notifications like this before.
>
> On Thu, Jan 16, 2020 at 20:08 Matt Sicker wrote:
>
> > I’ll watch for more moderation messages as new GitHub notifications come
> > through.
> >
> > On Thu, Jan 16, 2020 at 20:08 Mingshen Sun wrote:
> >
> &g
=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17017001
On Thu, Jan 16, 2020 at 6:04 PM Matt Sicker wrote:
>
> That works well enough I think. Thanks for the explanation!
>
> On Thu, Jan 16, 2020 at 19:16 Mingshen Sun wrote:
>
> > I just tested whether I can reply the GitHub no
on behalf of the archiver.
On Thu, Jan 16, 2020 at 5:03 PM Mingshen Sun wrote:
>
> Sorry for the late reply.
>
> Let me explain this again.
>
> Originally, GitBox will send notifications to dev@teaclave with
> issues/PRs/comments notifications, "making it seems that ther
That would just lead to double notifications still, wouldn't it?
> >
> > On Wed, 15 Jan 2020 at 12:49, Mingshen Sun wrote:
> > >
> > > The original GitBox notifications go to the notification@teaclave for
> > > archive:
> > > http://mail-archives.a
remove the first notification setup now.
> >
> > On Wed, 15 Jan 2020 at 10:02, Matt Sicker wrote:
> > >
> > > Still getting flooded with moderation messages for filtered messages.
> > >
> > > On Sun, 12 Jan 2020 at 18:53, Mingshen Sun wrote:
> > > >
Just give you guys an update on this. I have submitted the ticket but
still haven't been setup up. Hopefully, this will resolve this week.
Thanks.
- https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621
On Wed, Jan 8, 2020 at 11:43 AM Mingshen Sun wrote:
>
> Sure, I have sub
; On Wed, 8 Jan 2020 at 12:12, Mingshen Sun wrote:
> >
> > Thanks. I have notice this issue. One extra step is to put `
> > notificati...@github.com` into the dev list's whitelist. Should I contact
> > INFRA team or our moderators can get it done?
> >
> >
Thanks. I have notice this issue. One extra step is to put `
notificati...@github.com` into the dev list's whitelist. Should I contact
INFRA team or our moderators can get it done?
On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker wrote:
> Seems that some sort of archival service isn't actually
Added:
https://cwiki.apache.org/confluence/display/INCUBATOR/January2020#teaclave
To mentors, please sign off if it looks good to you. Thank you!
On Mon, Dec 30, 2019 at 11:55 PM Mingshen Sun wrote:
>
> Thanks, Matt.
>
> Let me copy the draft to the wiki. Feel fre
a problem.
>
> On Mon, Dec 30, 2019 at 01:08 Mingshen Sun wrote:
>
> > Hi all,
> >
> > I drafted a report for this month. Feel free to reply if I miss
> > something. Thanks.
> >
> > Mingshen
> >
> >
> > ## Teaclave
> >
> > Teaclave
-To: tvm.archi...@gmail.com
```
I'll try to use this method to manage the notifications in dev@teaclave.
[1] https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621
On Tue, Dec 24, 2019 at 12:19 PM Mingshen Sun wrote:
>
> I found that the TVM dev list [1] looks very clean and discussions on
ing's name and
brand. The VP, Brand has approve the project name.
(PODLINGNAMESEARCH-175)
On Sun, Dec 29, 2019 at 10:30 AM Mingshen Sun wrote:
>
> Hi Furkan, thanks for asking. I'll work on the report today.
>
> On Sun, Dec 29, 2019 at 10:29 AM Furkan KAMACI wrote:
> >
> >
On Mon, Dec 23, 2019 at 12:01 PM Mingshen Sun wrote:
> >
> > Hi, I just take a look at our lists. I suggest to move all auto-sent
> > GitBox mails (contain issues, PR and review comments synced with
> > GitHub for archive) to `notifications@`, and keep the `commits@` (only
Hi folks,
I'm polishing the readme of the project. The first thing is to have a
clear description of the project. The goal is to have a minimal and
clear description. I come up several paragraphs follow this outline:
- one-line description
- highlights in security
- highlights in function
-
wrote:
>
> Looks good to me!
>
> On Fri, Dec 13, 2019 at 13:05 Mingshen Sun wrote:
>
> > Hi Matt,
> >
> > I compose another diff for the `incubator-public` SVN truck to replace
> > all occurrences:
> >
> > Here is a summary:
> > ```
> >
ache.org
-
-
- .
- commits
- commits@mesatee.incubator.apache.org
-
-
- Bug tracking
- .
-
-https://issues.apache.org/jira/browse/XXX;>https://issues.apache.org/jira/browse/XXX
-
-
-
t; On Thu, 12 Dec 2019 at 22:58, Mingshen Sun wrote:
> >
> > Hi mentors,
> >
> > I'm working on the renaming issue [1] these days. One thing is about
> > name changes in whimsy [2]. It seems that I need to update the repo
> > (https://svn.apache.org/repos/as
-
- .
- commits
- commits@mesatee.incubator.apache.org
-
-
- Bug tracking
- .
-
-https://issues.apache.org/jira/browse/XXX;>https://issues.apache.org/jira/browse/XXX
-
-
-
-
901 - 987 of 987 matches
Mail list logo
