getssl
cli
getssl | cli | |
---|---|---|
9 | 8 | |
2,036 | 3,482 | |
0.3% | 0.7% | |
7.0 | 9.2 | |
14 days ago | 6 days ago | |
Shell | Go | |
GNU General Public License v3.0 only | 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.
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.
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?
boulder - An ACME-based certificate authority, written in Go.
jose-jwt - Ultimate Javascript Object Signing and Encryption (JOSE), JSON Web Token (JWT) and Json Web Keys (JWK) Implementation for .NET and .NET Core
certificates - 🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
slips - SatoshiLabs Improvement Proposals
uacme - ACMEv2 client written in plain C with minimal dependencies
authy - Go library and program to access your Authy TOTP secrets.
puppeteer - Node.js API for Chrome
ssh-baseline - DevSec SSH Baseline - InSpec Profile
acme-tiny - A tiny script to issue and renew TLS certs from Let's Encrypt
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
ssh-tools - Making SSH more convenient
sio-go - Authenticated encryption for streams in Go