From 5fa3bee7d82f8057bcdf95e2388b4afd1cbb80d8 Mon Sep 17 00:00:00 2001
From: Marco Franssen <marco.franssen@philips.com>
Date: Thu, 19 Aug 2021 12:57:27 +0200
Subject: [PATCH] Initial commit

---
 .editorconfig | 15 +++++++++++++++
 README.md     | 12 ++++++++++++
 2 files changed, 27 insertions(+)
 create mode 100644 .editorconfig
 create mode 100644 README.md

diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 0000000..a6f78e0
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,15 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+trim_trailing_whitespace = true
+insert_final_newline = true
+indent_size = 2
+tab_width = 2
+indent_style = space
+
+[*.go]
+indent_size = 4
+tab_width = 4
+indent_style = tab
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..bd85d18
--- /dev/null
+++ b/README.md
@@ -0,0 +1,12 @@
+# SPIFFE Vault
+
+Integrates [SPIFFE][spiffe] SVID authentication with [Hashicorp Vault][hashivault] to retrieve a `VAULT_TOKEN`.
+
+## Example usecases
+
+- Read secrets from Hashicorp Vault [Hashicorp Vault][hashivault] without providing a secret to authenticate against [Hashicorp Vault][hashivault]. Instead we will be using a [SPIFFE][spiffe] SVID to authenticate ourself against [Hashicorp Vault][hashivault].
+
+- Perform secretless/keyless code signing by utilizing the [Hashicorp Vault Transit engine](https://www.vaultproject.io/docs/secrets/transit) as a software defined HSM. This resolves the issue of having signing keys on a local machine as well resolves the issue of managing secrets to access the signing keys. Again we utilize the [SPIFFE][spiffe] SVID to authenticate against Hashicorp Vault.
+
+[hashivault]: https://vaultproject.org "hashicorp Vault"
+[spiffe]: https://spiffe.io "SPIFFE"