easy-rsa alternatives and similar tools
Based on the "Tools and web interfaces" category.
Alternatively, view easy-rsa alternatives based on common mentions on social networks and blogs.
5.0 10.0 L2 easy-rsa VS Sambahttps://gitlab.com/samba-team/samba is the Official GitLab mirror of https://git.samba.org/samba.git -- Merge requests should be made on GitLab (not on GitHub)
4.9 8.8 L3 easy-rsa VS OpenIDOpenID Certified™ OpenID Connect Relying Party implementation for Apache HTTP Server 2.x
4.7 9.5 L2 easy-rsa VS FreeIPAMirror of FreeIPA, an integrated security information management solution
2.5 9.0 easy-rsa VS BounCABounCA is a web tool to generate self-signed SSL certificates and setup a key infrastructure
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of easy-rsa or a related project?
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).
If you are looking for release downloads, please see the releases section on GitHub. Releases are also available as source checkouts using named tags.
For 3.x project documentation and usage, see the [README.quickstart.md](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 IRC at Freenode/#openvpn for general support or Freenode/#easyrsa for development discussion.
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.x, at present v3.x.x pre-release branches, used for staging branches release/2.x release/1.x
LICENSING info for 3.x is in the [COPYING.md](COPYING.md) file
Code style, standards
We are attempting to adhere to the POSIX standard, which can be found here: