-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
cacert: ensure that NIX_SSL_CERT_FILE is readable before using it #345322
base: staging
Are you sure you want to change the base?
Conversation
Following on from NixOS#303307, we check that `NIX_SSL_CERT_FILE` is readable from the current environment before using it; otherwise we set it from the cacert package as before. We log a message if we're inheriting it, as well as if we're ignoring it, to leave a breadcrumb for people wondering why their custom SSL cert file isn't being used. Fixes NixOS#345226.
echo "cacert/setup-hook: NIX_SSL_CERT_FILE in environment $NIX_SSL_CERT_FILE cannot be read; overriding" >&2 | ||
fi | ||
export NIX_SSL_CERT_FILE="@out@/etc/ssl/certs/ca-bundle.crt" | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking of this:
export NIX_SSL_CERT_FILE="${NIX_SSL_CERT_FILE:-@out@/etc/ssl/certs/ca-bundle.crt}"
if test ! -r "$NIX_SSL_CERT_FILE"; then
echo "cacert/setup-hook: NIX_SSL_CERT_FILE in environment $NIX_SSL_CERT_FILE cannot be read; overriding" >&2
export NIX_SSL_CERT_FILE="@out@/etc/ssl/certs/ca-bundle.crt"
fi
It's still a bit of duplication, but at least there's no edge cases around e.g. testing an empty file when NIX_SSL_CERT_FILE isn't set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the logging might be a bit verbose, but I believe this should fix the issue.
Is there something blocking this PR from getting merged? We are facing an issue that is fixed by this PR in our current setup. |
Nothing blocking it aside from attracting the attention / review of someone
with permission to merge, I'm afraid :/
…On Wed, 8 Jan 2025, 8:05 am Émile Grégoire, ***@***.***> wrote:
Is there something blocking this PR from getting merged? We are facing an
issue that is fixed by this PR in our current setup.
—
Reply to this email directly, view it on GitHub
<#345322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADOXCXXGBMVJCTP2EKS3D2JQ6QZAVCNFSM6AAAAABPB3F5DOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZWGIYTONRYGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Description of changes
Following on from #303307, we check that
NIX_SSL_CERT_FILE
is readable from the current environment before using it; otherwise we set it from the cacert package as before.We log a message if we're inheriting it, as well as if we're ignoring it, to leave a breadcrumb for people wondering why their custom SSL cert file isn't being used.
Fixes #345226.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.