cloudnative-pg / cloudnative-pg/plugin-barman-cloud
[Request] - support encrypt files before pushing to object store
- Lenguaje dominante
- Go
- Estrellas
- 191
- Forks
- 72
- Merge medio
- 2 d 21 h
- PR fusionados (30 d)
- 21
Descripción
As best as I can tell, the only [options for tuning encryption](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#EncryptionType) are 'passed through' to the underlying `s3` (or compatible) API calls.
If it turns out that I'm wrong on that one, please let me know!
My question/request: allow use of symmetric encryption _before_ the files leave the host and are sent off to the object store.
I think this could be as straight forward as passing in a key/cypher to the [underlying archiver](https://github.com/cloudnative-pg/plugin-barman-cloud/blob/9be87b0d9c87c0df7f1f72caa33bf848fbc16582/internal/cnpgi/common/wal.go#L147)
The motivation: not all object stores support "BYO" key for bucket encryption and even if they do, you're still required to hand the sensitive key material off to the remote backend so that it can encrypt things for you. One of the simplest ways to address this is to encrypt objects before they're ever off the host.
Symmetric encryption is sufficient for "at rest, I need to know that I truly am the only person that can read it" needs.
Guía de contribución
Línea de trabajo
Start with the EncryptionType API and internal/cnpgi/common/wal.go at the linked archiver call. Trace how WAL files are handed to the archiver and how encryption options reach the object-store API; done requires a defined symmetric-encryption configuration and verified protection before upload.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- go
- Área
- cloud, security
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100