You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
There seems to be an issue with the configuration priority of environment variables #1404
In the EasyRSA-Advanced.md document, it says that EasyRSA gives higher priority to environment variables over the vars file. However, even after I set the environment variables, it still used the configurations from the vars file.
Does your vars file have the EASYRSA_CERT_EXPIRE configuration enabled? Based on my testing, if this option is configured in the vars file, it will always use the value from there; only when it’s commented out will the environment variable setting take effect.
Activity
TinCanTech commentedon Nov 5, 2025
Which version of
easyrsais that and on what OS ?cuutt commentedon Nov 5, 2025
Alpine Linux 3.22
EasyRSA 3.2.4
TinCanTech commentedon Nov 5, 2025
Works for me ..
cuutt commentedon Nov 6, 2025
Does your vars file have the EASYRSA_CERT_EXPIRE configuration enabled? Based on my testing, if this option is configured in the vars file, it will always use the value from there; only when it’s commented out will the environment variable setting take effect.
TinCanTech commentedon Nov 6, 2025
So, you are saying that, your
varsfile is resetting an externally set variable ?cuutt commentedon Nov 6, 2025
yes
TinCanTech commentedon Nov 6, 2025
Your
varsfile is not supported, take a look atvars.examplein the source.cuutt commentedon Nov 6, 2025
It really was a problem with the format of the vars file — I didn’t expect it to still work.
cuutt commentedon Nov 6, 2025
Thank you very much for your answer.
TinCanTech commentedon Nov 6, 2025
Closed-as: archived.
This looks like a glitch in the main-frame: #1404 (comment)
TinCanTech commentedon Nov 8, 2025
source_vars()couldgrepforset_var.