certificates
cfssl
Our great sponsors
certificates | cfssl | |
---|---|---|
40 | 24 | |
6,154 | 8,457 | |
3.0% | 1.4% | |
9.5 | 7.5 | |
6 days ago | 11 days ago | |
Go | Go | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
certificates
-
You shouldn't run NSA-grade Wi-Fi at home
You can roll your own with https://github.com/smallstep/certificates. We maintain major open source projects and contribute a lot to other projects. I don’t think that means everything we do has to be open source. Sorry this one wasn’t. Doing this in pure open source would be a book, not a blog post.
Love Let’s Encrypt — we’re sponsors — but using them for WiFi is a terrible idea. You need internal PKI for WiFi.
- Running one’s own root Certificate Authority in 2023
-
Distributing ACME Let'sEncrypt certs for homelab
letsencrypt was always about moving the public internet off of http, it doesn't really make sense to use it throughout your internal network. but if you really want TLS and ACME for auto renewal, other solutions are available: https://github.com/smallstep/certificates
-
SSH With SSO
You could try step-ca: https://github.com/smallstep/certificates. There’s an OIDC provisioner for SSO and you can sign (short-lived) SSH certificates with it.
-
Web application to manage self-signed certificate authorities/certificates/keys
You could also check out out Step CA: https://github.com/smallstep/certificates and the accompanying CLI. It has an ACME server and other methods for requesting certificates. It can work/integrate with your existing root(s), too.
- Selfhosted CA tutorial
-
ACME setup. Domain required?
This is a lot more complicated setup but it works for me. I run a private CA called step-ca from smallstep and it provides CA and ACME endpoint. I use a .home domain. The trick is the validation for non-http devices which is typically the DNS-01 challenge. For this, I have unbound in pfsense setup to work with acme-dns so I can keep everything internal. Again its complicated but if your learning cyber security it might help get a handle on all things TLS. Btw way behind the scenes I think the ACME plugin is really just running acme.sh bash script which is really good. Final reminder as other have stated. Private CA is great but you need to distro the roots and intermediates out to your clients for trust. If all your trying to do is have an https web gui for pfsense from one device its pretty easy.
-
A convert from Judaism to Catholicism goes to r/Catholicism to ask if it would be appropriate to pass down a century old Jewish prayer shawl to his son. Not everyone is welcoming.
Just a little heads up https://smallstep.com/certificates/
-
Looking for an open source certificate management solution.
Step-ca: Not web based, but the CLI is pretty user friendly: https://smallstep.com/certificates/
-
Using k8s-apiserver as AAA server for microservices?
I was just looking at https://smallstep.com/certificates a few days ago. It looks like they have an operator that fits your description as well as example docs for setting up inter-microservice mtls.
cfssl
- Running one’s own root Certificate Authority in 2023
- Selfhosted CA tutorial
-
i must be the only guy that understands certificates
cfssl is kinda outright better version of that.
-
SSL certificate problem: unhandled critical extension
The Cloudflare SSL tools at https://github.com/cloudflare/cfssl might help. Here's what it shows for one of the example Snake Oil certs:
-
Private CA management
I've used this in the past and it worked great. https://github.com/cloudflare/cfssl
- Linux Certificate Authority root stores have a too simple view of 'trust'
- Creating an internal Certificate Authority in 2022 that is accepted by modern web browsers.
-
How to create users in Kubernetes
The first step is to create the source key that represents our user. This key is created using a tool like openssl but another popular tool to use is cfssl, created by Cloudflare. Some folks think cfssl is easier to use, and it definitely looks easier to script. But for this example we will use openssl. You can also choose to create the key using a number of different algorithms. For this example we will use ED25519.
-
[Legal notice] IoT Core will be discontinued on Aug. 16, 2023
TLS/SSL worked well with client certificates generated by the CFSSL API.
-
Feedback on a Self-signed SSL CA?
Not sure if relevant but we used tooling from CloudFlare in the past: https://github.com/cloudflare/cfssl
What are some alternatives?
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
OpenSSL - TLS/SSL and crypto library
boulder - An ACME-based certificate authority, written in Go.
easy-rsa - easy-rsa - Simple shell based CA utility
omgwtfssl - SSL certificate generation for developers who don't TLS good
LetsEncrypt-PRTG - Post request script to install an SSL certificate obtained with Certify the Web or win-acme in PRTG.
acme.sh - A pure Unix shell script implementing ACME client protocol
traefik-certs-dumper - Dump ACME data from Traefik to certificates
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
pam-ussh - uber's ssh certificate pam module
step - An async control-flow library that makes stepping through logic easy.