boulder
| boulder | bulletproof-tls | |
|---|---|---|
| 11 | 1 | |
| 4,983 | 355 | |
| 0.5% | - | |
| 9.6 | 10.0 | |
| 4 days ago | over 7 years ago | |
| Go | ||
| Mozilla Public 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.
bulletproof-tls
-
Should you use Let's Encrypt for internal hostnames?
> By the way, EasyRSA still isn't that easy, but it's better than using OpenSSL directly.
The trouble with EasyRSA (and similar tools) is that they make decisions for you and restrict what's possible and how. You're right about OpenSSL too, to use it directly requires a significant time investment to understand a lot about PKI.
I tried to address this problem with documentation and templates. Here's a step by step guide for creating a private CA using OpenSSL, including intermediate certificates, revocation, and so on: https://www.feistyduck.com/library/openssl-cookbook/online/c... Every aspect is configurable, and here are the configuration templates: https://github.com/ivanr/bulletproof-tls/tree/master/private...
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.
getssl - obtain free SSL certificates from letsencrypt ACME server Suitable for automating the process on remote servers.
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.
acmez - Premier ACME client library for Go
proposals - A home for well-formed proposed incubations for the web platform. All proposals welcome.
cli - 🧰 A zero trust swiss army knife for working with X509, OAuth, JWT, OATH OTP, etc.
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.
cert-manager-webhook-ovh - OVH Webhook for Cert Manager
certin - Go lib (and CLI) for quick creation of TLS keys and certificates for use in tests