9fda11d04f
The original cert_dates(); was intended to restrict certificate renewal to a fixed 30-day-window of the certificate expiry date. This was an unnecessary restriction. Removed-by: #594 The original cert_dates(); "gave rise to" the Easy-RSA "ambition" to support multiple versions of 'date' (*nix), which proved to be more demanding than initially expected. The "new" code speaks for itself. Currently supported versions of 'date', as of this pull request: * Linux (Standard Ubuntu) * FreeBSD * MacOS and MacOS Ports * busybox New functions: * cert_date_to_timestamp_s() Takes* an X509 certificate date, as output by SSL option '-startdate' or '-enddate' and creates a 'timestamp' in seconds since epoch. * offset_days_to_cert_date() [Note: 'days' not 'date'] Adds* the $offset number of days to the current date and creates an X509 "style" certificate date string. * ff_date_to_cert_date() Takes* a fixed-format date and converts it into an X509 certificate "style" date string. * ssl_cert_not_before_date() Dedicated function to return an X509 certificate '-startdate' by SSL. * ssl_cert_not_after_date() Dedicated function to return an X509 certificate '-enddate' by SSL. These functions serve to provide an extensible frame-work for Easy-RSA to manage all 'date' requirements. Extras: Built in reports 'show-expire','show-revoke' and 'show-renew' all use these functions to interrogate index.txt and the PKI, extensively. Add error detection to Easy-RSA options which involve "number of days" and fail for any input which is not a base-10 number. eg. --days=nn Closes: #593 Signed-off-by: Richard T Bonhomme <tincantech@protonmail.com>
Overview
easy-rsa is a CLI utility to build and manage a PKI CA. In laymen's terms, this means to create a root certificate authority, and request and sign certificates, including intermediate CAs and certificate revocation lists (CRL).
Downloads
If you are looking for release downloads, please see the releases section on GitHub. Releases are also available as source checkouts using named tags.
Documentation
For 3.x project documentation and usage, see the README.quickstart.md file or the more detailed docs under the doc/ directory. The .md files are in Markdown format and can be converted to html files as desired for release packages, or read as-is in plaintext.
Getting help using easy-rsa
Currently, Easy-RSA development co-exists with OpenVPN even though they are separate projects. The following resources are good places as of this writing to seek help using Easy-RSA:
The openvpn-users mailing list is a good place to post usage or help questions.
You can also try libera.chat IRC network, in channels #openvpn for general support or #easyrsa for development discussion.
Branch structure
The easy-rsa master branch is currently tracking development for the 3.x release cycle. Please note that, at any given time, master may be broken. Feel free to create issues against master, but have patience when using the master branch. It is recommended to use a release, and priority will be given to bugs identified in the most recent release.
The prior 2.x and 1.x versions are available as release branches for tracking and possible back-porting of relevant fixes. Branch layout is:
master <- 3.1, at present
v3.x.x pre-release branches, used for staging branches
release/3.0 v3.0.x bugfix/security/openssl updates
release/2.x
release/1.x
LICENSING info for 3.x is in the COPYING.md file
Code style, standards
We are attempting to adhere to the POSIX standard, which can be found here: