TinCanTech
TinCanTech
Using Windows, `easyrsa` is always in the same place as `openssl-easyrsa.cnf`, unless the user has made specific changes, which `easyrsa` does not have to support. Other OSs (*nix), if EasyRSA...
I am tempted to include all the data files as `heredoc`s inside `easyrsa`. Extra 16.0 kB
### BUG: If `easyrsa` is in your path, **not** in the current-directory, then it will always **fail** to find `openssl-easyrsa.cnf`. This is due to the current mess found in `vars_setup()`....
It seems like nobody knows how to package EasyRSA. Packaging found at: - **Arch Linux** - `/etc/easyrsa` `easyrsa` is installed to `/usr/bin` but fails to find `openssl-easyrsa.cnf` - **Debian 10**...
In order to allow `easyrsa` to be executed from a location in `PATH`, `EASYRSA` should be `$PWD`. `prog_dir` can be used to look for data files, they _might_ be present...
Because finding the data files is **critical** for `easyrsa`, the best location for them is: `/etc/easyrsa`
Because the `x509-types` and data-files are intended to be edited by users, they need to be per PKI. It makes sense for `init-pki` to copy the `x509-types` and data-files **from**...
@Prouflon Thanks for your feedback, you can clearly see the problem. I have a patch, almost ready, which will sort this mess out. I'll post it as a draft and...
There is one question: - Where should `vars` belong ? It is customary to find `vars` in the parent folder to the PKI. This can be copied/moved to the PKI...
I need the output to this on Windows 11 with and without WSL: ``` $ readlink -f ./easyrsa $ echo "$PWD" $ set ```