TinCanTech
TinCanTech
Work-around above will do.
This still bugs me. Another example: - `build-server-full 001.002.003.004` Result: Subject: commonName = 001.002.003.004 X509v3 Subject Alternative Name: IP Address:1.2.3.4
The basic fact is this: - EasyRSA should NOT **assume** that a server with `commonName` equal to `1.2.3.4` should have a `subject alternative name` equal to `IP:1.2.3.4`. EasyRSA should behave...
Related: #1086
Following from #1088 I believe that Easy-RSA offers suitable methods to configure SAN as required and that the automatic creation of an ipv4-address SAN is obsolete. The resolution here is...
Closed via 0b85a5d
The original question here is bogus. Adhering to POSIX is clearly a simpler task than providing specific OS support. Until there is a POSIX deal-breaker, EasyRSA is POSIX compliant.
This _issue_ has been resolved. EasyRSA command `renew` will correctly **renew** a certificate.
If _you_ can support bash completion for EasyRSA then, please, feel free to reopen. Until then, closed as not planned.
As soon as I closed this I changed my mind. Sorry for the noise. Re-opened as "_would really like this but want help_". I have put a lot of work...