TinCanTech
TinCanTech
`easyrsa3` has **never** honoured those `openssl` options.
> This is a bug You make me laugh.. Closing as noise.
@QueuingKoala I cannot see a reason to delay merging this, are you still interested ? Ref: https://github.com/QueuingKoala/easyrsa3/commit/448ee272f5f500facef9cdc9b9711bfeaf82e55c
`easyrsa` can now be successfully used from PATH and all data-files will be placed in the current PKI. The only exception being `vars`, due to user expectations.
All user data files now belong in the PKI or system shared areas. `easyrsa` can be run from `$PATH` with `--pki-dir`, which means you could do: ``` $ easyrsa --pki-dir=/home/tct/easy-rsa/family...
@viharm I do not understand your question. Please start a new issue with **full details**.
@viharm Your question is **not** related to this issue.
This is already possible and simple. Even Sub-CA support. Closing
@cron2 - I rolled back to `OpenVPN-2.5-beta3-I602-x86.msi`, the status was also `unknown`. 2.4.9 - status `unknown` 2.4.7 ``` C:\Users\IEUser\Desktop>ipconfig /all Windows IP Configuration Host Name . . . . ....
2.4.8 may have been _neglected_ ...