Skip to content

remote_cache: Refuse an empty signing certificate - #298

Merged
martinpitt merged 1 commit into
amutable-systems:mainfrom
daandemeyer:push-tpzsqunqslmo
Oct 12, 2026
Merged

martinpitt merged 1 commit into
amutable-systems:mainfrom
daandemeyer:push-tpzsqunqslmo

Conversation

@daandemeyer

Copy link
Copy Markdown
Member

A builder whose certificate file is empty signs results without a
certificate, because the signer reads an empty file as no certificate at
all. The signer then also skips the check that the certificate outlives the
results. Parse the certificate file whenever it is configured, so an empty
file fails like any other unusable certificate.

Signed-off-by: Daan De Meyer daan@amutable.com

A builder whose certificate file is empty signs results without a
certificate, because the signer reads an empty file as no certificate at
all. The signer then also skips the check that the certificate outlives the
results. Parse the certificate file whenever it is configured, so an empty
file fails like any other unusable certificate.

Signed-off-by: Daan De Meyer <daan@amutable.com>
@martinpitt
martinpitt merged commit 7a2f119 into amutable-systems:main Oct 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants