certificates
cli
certificates | cli | |
---|---|---|
40 | 8 | |
6,211 | 3,506 | |
2.0% | 1.3% | |
9.5 | 9.2 | |
5 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
cli
-
Google will disable all but OAuth for IMAP, SMTP and POP starting Sept. 30
https://github.com/smallstep/cli implements some OAuth flows from the CLI, it may be helpful for you.
- Running one’s own root Certificate Authority in 2023
- Uacme: ACMEv2 client written in plain C with minimal dependencies
-
OpenSSL as a GUI
Is the according command line tool (https://github.com/smallstep/cli) from smallstep free and behind this GUI?
-
If you’re not using SSH certificates you’re doing SSH wrong
And they have an open issue for producing a chocolatey package: https://github.com/smallstep/cli/issues/365
-
Should you use Let's Encrypt for internal hostnames?
I'm biased because I'm the founder of the company, but you should check out the certificate management toolchain (CA[1] and CLI[2]) we've built at smallstep. A big focus of the project is human-friendliness. It's not perfect (yet) but I think we've made some good progress.
We also have a hosted option[3] with a free tier that should work for individuals, homelabs, pre-production, and even small production environments. We've started building out a management UI there, and it does map to the CLI as you've described :).
[1] https://github.com/smallstep/certificates
[2] https://github.com/smallstep/cli
[3] https://smallstep.com/certificate-manager/
-
SSH Keys How Are You Managing Them All?
https://github.com/smallstep/cli is pretty amazing, tbh. Documentation is just as stellar!
-
Recommend: Linux-Equivalent Tool of mkcert
https://github.com/smallstep/cli may be a bit overkill for your needs, but it's an epic toolkit and well worth checking out!
What are some alternatives?
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
jose-jwt - Ultimate Javascript Object Signing and Encryption (JOSE), JSON Web Token (JWT) and Json Web Keys (JWK) Implementation for .NET and .NET Core
boulder - An ACME-based certificate authority, written in Go.
slips - SatoshiLabs Improvement Proposals
omgwtfssl - SSL certificate generation for developers who don't TLS good
authy - Go library and program to access your Authy TOTP secrets.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
ssh-baseline - DevSec SSH Baseline - InSpec Profile
easy-rsa - easy-rsa - Simple shell based CA utility
traefik-certs-dumper - Dump ACME data from Traefik to certificates
sio-go - Authenticated encryption for streams in Go