udf2457

Ah ok, that sort of thing wasn't at all clear from my reading of your docs which, understandably, takes a route of showing "create and restore to the same". Unless...

Useful references: https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/generic/README.md#provenance-for-goreleaser https://goreleaser.com/blog/slsa-generation-for-your-artifacts/#slsa-github-generator

Hi Brave (a.k.a. Chrome)

I see, thanks @nevun . The trouble with `--recv-key` is implies trust ? Might be better to publish an aggregated file of all keys that could be downloaded and imported...

Honestly I'm surprised there's no PIV / PKCS#11 support in SPIRE, let alone TPM support. Would have thought it would be an obvious necessity to acheive hardware-backed node attestation and...

Edit to add: I think I might have stumbled across a bug. :wink: Looking more closely at my `pgbackrest.conf` I noticed I was missing `repo2-type=s3` after adding that and re-running...

Apologies for the delay on this @dwsteele, have been busy at $work, but am hoping to test it over the next couple of days. Test and compile off main branch,...

Apologies, I don't know my way around `meson`. I cloned my repo but `meson` is refusing to have to do anything with it: `build/pgbackrest/doc/src/meson.build:5:4: ERROR: Problem encountered: meson is currently...

@dwsteele Tested using quickstart with the following config: ``` [demo] pg1-path=/var/lib/postgresql/16/main [global] repo1-retention-full=2 repo1-type=s3 repo1-s3-endpoint= repo1-s3-bucket= repo1-s3-key= repo1-s3-key-secret= repo1-s3-region=ch-gva-2 repo1-s3-sse-customer-key= ``` It was tested against [Exoscale SOS](https://community.exoscale.com/documentation/storage/encryption/) ``` 2024-04-14 13:18:26.247...

As an aside @dwsteele , you need to do whatever you need to do to ensure the SSE key gets replaced with `` for `repo1-s3-sse-customer-key`, like you already do for...