Re: Podling Teaclave Report Reminder - January 2021

2021-01-08 Thread Dave Fisher
Hi -

I'm your Incubator Shepherd for this report.

You need to provide the name of the committer you added. Has Teaclave ever 
added to the PPMC? If so then provide that.

Also what version was the release?

Regards,
Dave

On 2021/01/07 15:29:32, Matt Sicker  wrote: 
> Looks good to me!
> 
> On Wed, 6 Jan 2021 at 19:23, Mingshen Sun  wrote:
> >
> > Dear Teaclave community,
> >
> > Here is the report for 2020 Q4. Feel free to comment on the report. Thanks.
> >
> > To mentors, I have uploaded the report to the wiki page. [1]
> >
> > Best,
> > Mingshen
> >
> > [1] 
> > https://cwiki.apache.org/confluence/display/INCUBATOR/January2021#teaclave
> >
> > ## 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. Improve project structure and documentation
> >   2. Grow the community (attracting more committers, contributors, users)
> >   3. Publish more Apache releases
> >
> > ### Are there any issues that the IPMC or ASF Board need to be aware of?
> >
> > None.
> >
> > ### How has the community developed since the last report?
> >
> > - We received contributions from a new external contributor.
> > - We found a new project using Teaclave SGX SDK called Veracruz, which is a
> >   framework for defining and deploying collaborative, privacy-preserving
> >   computations amongst a group of mutually mistrusting individuals.
> > - We summarized the community and projects powered by Teaclave and published
> >   a blog on our homepage.
> > - Rust TrustZone SDK will be accepted in Teaclave as a subproject. The 
> > community
> >   is discussing and voting the acceptance.
> > - The community has accepted a new committer.
> >
> > ### How has the project developed since the last report?
> >
> > - Add PCA function in the builtin executor.
> > - Add exposed password checking function in the builtin executor.
> > - Add the attestation subcommand to display attestation reports form
> > the Intel attestation service.
> > - Add document to support deploying on Azure confidential computing VM.
> >
> >
> > ### How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   - [ ] Initial setup
> >   - [ ] Working towards first release
> >   - [x] Community building
> >   - [ ] Nearing graduation
> >   - [ ] Other:
> >
> > ### Date of last release:
> >
> >   2020-10-09
> >
> > ### When were the last committers or PPMC members elected?
> >
> >   2020-10-22
> >
> > ### Have your mentors been helpful and responsive?
> >
> > Yes, our mentors are very helpful and responsive on our discussion
> > about security
> > reporting and new projects acceptance voting.
> >
> > ### Is the PPMC managing the podling's brand / trademarks?
> > We don't find any 3rd parties incorrectly using the podling's name and 
> > brand.
> > The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175)
> >
> > On Wed, 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:
> > > >
> > > > A reminder to discuss and submit a report.
> > > >
> > > > Thanks,
> > > > Dave
> > > >
> > > > On 2020/12/24 00:35:06, jmcl...@apache.org 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 board report.
> > > > >
> > > > > The board meeting is scheduled for Wed, 20 January 2021.
> > > > > The report for your podling will form a part of the Incubator PMC
> > > > > report. The Incubator PMC requires your report to be submitted 2 weeks
> > > > > before the board meeting, to allow sufficient time for review and
> > > > > submission (Wed, January 06).
> > > > >
> > > > > Please submit your report with sufficient time to allow the Incubator
> > > > > PMC, and subsequently board members to review and digest. Again, the
> > > > > very latest you should submit your report is 2 weeks prior to the 
> > > > > board
> > > > > meeting.
> > > > >
> > > > > Candidate names should not be made public before people are actually
> > > > > elected, so please do not include the names of potential committers or
> > > > > PPMC members in your report.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > The Apache Incubator PMC
> > > > >
> > > > > Submitting your Report
> > > > >
> > > > > --
> > > > >
> > > > > Your report should contain the following:
> > > > >
> > > > > *   Your project name
> > > > > *   A brief description of your project, which assumes no knowledge of
> > > > > the project or necessarily of its field
> > > > > *   A list of the three most important 

Re: [apache/incubator-teaclave-sgx-sdk] Are git tags being mutated? (#303)

2021-01-08 Thread Adam Szkoda
Thank you for clarifying @dingelish

-- 
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/303#issuecomment-756982675

Re: [apache/incubator-teaclave-sgx-sdk] Encrypted websockets in SGX (#291)

2021-01-08 Thread Claus M
Hey, thanks for looking into this  

The echo server was just a test to get it to work at all, I'll try to reproduce 
with my actual web server and then come back to you. I checked the ciphers and 
they _should_ be supported, but I'll need a few days to reproduce. I'll respond 
here then. 

Cheers!

-- 
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/291#issuecomment-756941231