boulder
cli
boulder | cli | |
---|---|---|
11 | 8 | |
4,983 | 3,487 | |
0.5% | 0.8% | |
9.6 | 9.2 | |
4 days ago | 4 days ago | |
Go | Go | |
Mozilla Public 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.
boulder
-
Trying to do something a bit crazy
There's no reason you couldn't run your own ACME server (the Let's Encrypt folk publish an open source one, boulder, but there's plenty of others). Then you can just use certbot in your VMs to manage certificates, configured to point to your CA server instead of the Let's Encrypt one.
-
Raise a toast if you've ever used Lets Encrypt
Let's Encrypt's ACME server is open source: https://github.com/letsencrypt/boulder
-
Should you use Let's Encrypt for internal hostnames?
GP's post prompted me to look into LE's ACME server implementation, Boulder [1], but it's pretty apparent that Boulder is not suitable for small scale deployments. But the smallstep "certificates" project seems to be a lot more reasonable for this use-case. Thanks for sharing, I'll definitely check it out!
[1]: https://github.com/letsencrypt/boulder
-
How to automate regular renewal certificates for a private CA?
There's also Boulder too which supposedly is what Let's Encrypt actually runs. But, I believe you have be running Python or Docker on your Linux server, where SmallStep didn't have that requirement.
- Self-hosted WUI Internal CA is needed. What would you suggest?
- r/crypto - Let's Encrypt's recommended reading list
- Let's Encrypt's recommended reading list
-
is it OK to use Free SSL/TLS Certificates - Let's Encrypt ?
Actually it is Open Source (I'd say "Free Software" but they're the same thing). The software that makes the CA work, Boulder, is here: https://github.com/letsencrypt/boulder and the end user software to get certificates which now called CertBot but was once just named "letsencrypt" is here: https://github.com/certbot/certbot
-
The Next Gen Database Servers Powering Let's Encrypt
Why are you assuming that their workload includes just one query per emitted certificate?
The reality is that they are storing information during challenges, implementing rate limiting per-account, supporting OCSP validation and a few other things.
You can investigate further if you really want to see the queries that they make against the database since their software (Boulder) is open source [1]. Most queries are in the files in the "sa" (storage authority) folder.
[1] https://github.com/letsencrypt/boulder/
-
Why Let's Encrypt decided for EPYC instead of Xeon for their database
They won't pay any licensing fees at all when their whole stack is open source. They even wrote their own CA from scratch.
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?
certificates - 🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
jose-jwt - Ultimate Javascript Object Signing and Encryption (JOSE), JSON Web Token (JWT) and Json Web Keys (JWK) Implementation for .NET and .NET Core
pki - The Dogtag Certificate System is an enterprise-class Certificate Authority (CA) which supports all aspects of certificate lifecycle management, including key archival, OCSP and smartcard management.
slips - SatoshiLabs Improvement Proposals
acmez - Premier ACME client library for Go
authy - Go library and program to access your Authy TOTP secrets.
getssl - obtain free SSL certificates from letsencrypt ACME server Suitable for automating the process on remote servers.
ssh-baseline - DevSec SSH Baseline - InSpec Profile
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
bulletproof-tls
sio-go - Authenticated encryption for streams in Go