Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add presentation from EuroProofNet24 WG3, Dresden #154

Merged
merged 1 commit into from
Mar 29, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions resources/2024-03-28-europroofnet24.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
slug: 2024-03-28-europroofnet24
title: "Enarx & Steward Attestation"
authors: [richard]
tags: [Event]
---

**Title**: Enarx & Steward Attestation
**Author**: Richard Zak
**Date**: March 28, 2024

A discussion on how Enarx and [Steward](https://github.com/enarx/steward) use [Certificate Signing Requests](https://en.wikipedia.org/wiki/Certificate_signing_request) (CSRs) to provide remote attestation of a Keep. Steward is a Confidential Computing-aware [Certificate Authority](https://en.wikipedia.org/wiki/Certificate_authority) which signs CSRs if and only if all attestation checks are successfully validated. This way, the signed certificate, which is part of the Steward CA certificate chain, becomes a token for third parties to ensure that an application secured with Enarx *really* is secured.

**Source**: EuroProofNet 2024 Working Group 3

**Link**: https://europroofnet.github.io/wg3-dresden24/

**PDF**: [Enarx_Steward_Attestation_EuroProofNet24.pdf](/assets/docs/Enarx_Steward_Attestation_EuroProofNet24.pdf)
Binary file not shown.