Crypt-LE
lego
Crypt-LE | lego | |
---|---|---|
1 | 56 | |
348 | 7,324 | |
- | 1.9% | |
2.7 | 8.9 | |
about 1 year ago | 10 days ago | |
Perl | Go | |
Artistic License 2.0 | MIT License |
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.
Crypt-LE
-
Help me understand Wildcard Certs
Normally you can use the same .csr forever if the domain is the same - I normally use LE64 to generate let's encrypt certificates (which can do wildcards also), but if you're purchasing a certificate rather than generating a free one, and you want to generate it right in IIS, you can follow a guide like this. If you generate a wildcard cert like *.domain.com, you can use it for all your subdomains but NOT generally for domain.com itself (depending on your application). You can use the same certificate for all applications provided they support whatever format the certificate is in; mostly these will be in PEM-style anymore so you have the whole cert chain in one file.
lego
-
Take a look at traefik, even if you don't use containers
This is one area where I've found nixos to be really helpful. I can set this up with just adding some lines to the configuration.nix (which uses [lego](https://github.com/go-acme/lego) and letsencrypt in the backend):
```nix
-
Dehydrated: Letsencrypt/acme client implemented as a shell-script
Self contained but hardly a tiny supply chain attack surface: https://github.com/go-acme/lego/blob/master/go.sum
-
Running one’s own root Certificate Authority in 2023
This ACME client looks promising, but I haven’t tried it yet: https://github.com/go-acme/lego
-
I am once again asking that "web" and "fullstack" developers...
My favorite method of obtaining certificates is with lets encrypt and LEGO
-
Where do you get/setup certificates from for your https/ssl?
Caddy where possible, and acme.sh or lego where not.
- Anyone using WireGuard with a domain name? Any ideas to lower the bills?
- Acme.sh runs arbitrary commands from a remote server
-
How do you renew SSL certificates?
Depend on host's capability... - lego - dehydrated - caddy - in case it already works as a web server, it will automatically issue and renew certs
- Automating LE renewals with dns-01?
-
LeGo CertHub v0.9.0 with Docker Support
u/gregtwallace maybe in the short term until you write your own, you could provide a hook into one of the many ACME client implementations which do DNS-01 and support the majority of major DNS provider APIs out of the box? That would make your (really great!) project much more widely usable.
What are some alternatives?
caddy-cloudflare - Caddy with integrated support for Cloudflare DNS-01 ACME verification challenges.
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.
Netdot - Network Documentation Tool
acme.sh - A pure Unix shell script implementing ACME client protocol
mod_md - Let's Encrypt (ACME) in Apache httpd
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
HandyAcme - A TypeScript Client implements ACME (RFC 8555)
autocert - [mirror] Go supplementary cryptography libraries
sslmgr - A layer of abstraction the around acme/autocert certificate manager (Golang)
acmetool - :lock: acmetool, an automatic certificate acquisition tool for ACME (Let's Encrypt)
certify - Professional ACME Client for Windows. Certificate Management UI, powered by Let's Encrypt and compatible with all ACME v2 CAs. Download from certifytheweb.com
ACL - A simple but powerful Access Control List manager