getssl
boulder
getssl | boulder | |
---|---|---|
9 | 11 | |
2,036 | 4,981 | |
0.3% | 0.5% | |
7.0 | 9.6 | |
14 days ago | 6 days ago | |
Shell | Go | |
GNU General Public License v3.0 only | 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.
getssl
-
Why Certificate Lifecycle Automation Matters
A 'competitor' to this would be GetSSL which is a pure-shell ACME client (plus OpenSSL and cURL) and can be executed on one host, but send verification tokens to remote systems (where you may not have cron access):
> Get certificates for remote servers - The tokens used to provide validation of domain ownership, and the certificates themselves can be automatically copied to remote servers (via ssh, sftp or ftp for tokens). The script doesn't need to run on the server itself. This can be useful if you don't have access to run such scripts on the server itself, as it's a shared server for example.
* https://github.com/srvrco/getssl
-
why should we use ssl certificates for our self-hosted services in our internal network?
I first got by with self signed certificates, but with all the major browsers warning they'll stop supporting those eventually I finally bit the bullet last month and installed getssl to automatically update all my certificates once a month.
-
letsencrypt with noip free domain?
because I didn't want to install another package manager (snapd) on my Ubuntu 18.04 server I checked the ACME Client Implementations page and decided to try getssl, a nice little shell script that does everything I need and then some.
-
Running certbot container on schedule without cron?
I just have a dedicated container that runs getssl everyday. Anything that has a web interface (Or anything that requires TLS) gets it's own conf file that gets added to the daily check. Each conf file tells getssl how to load the certificate for its particular service.
-
LetsEncrypt / CertBot without snapd?
I have been using https://github.com/srvrco/getssl for years on my raspberry pi. It's a much simpler Bash script that doesn't break after every update.
- Uacme: ACMEv2 client written in plain C with minimal dependencies
- Any reason NOT to use Debian-provided Certbot?
-
Old files keep appearing bug
i have a problem where after installing getssl (https://github.com/srvrco/getssl) to /root/.getssl i populated it's contents with bunch of SSL files using Dockerfile's COPY command. And now no matter what i do they keep reappearing.
-
Should you use Let's Encrypt for internal hostnames?
> acme.sh
Another shell-based ACME client I like is dehyradted. But for sending certs to remote systems from one central area, perhaps the shell-based GetSSL:
> Obtain SSL certificates from the letsencrypt.org ACME server. Suitable for automating the process on remote servers.
* https://github.com/srvrco/getssl
In general, what you may want to do is configure Ansible/Puppet/etc, and have your ACME client drop the new cert in a particular area and have your configuration management system push things out from there.
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.
What are some alternatives?
cli - 🧰 A zero trust swiss army knife for working with X509, OAuth, JWT, OATH OTP, etc.
certificates - 🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
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.
uacme - ACMEv2 client written in plain C with minimal dependencies
acmez - Premier ACME client library for Go
puppeteer - Node.js API for Chrome
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.
acme-tiny - A tiny script to issue and renew TLS certs from Let's Encrypt
bulletproof-tls
ssh-tools - Making SSH more convenient
cert-manager-webhook-ovh - OVH Webhook for Cert Manager