daemon
a personal web server, one line of config to add a reverse proxy (by fsmv)
certificates
🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH. (by smallstep)
| daemon | certificates | |
|---|---|---|
| 2 | 40 | |
| 11 | 6,211 | |
| - | 2.0% | |
| 8.3 | 9.5 | |
| 4 months ago | 4 days ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
daemon
Posts with mentions or reviews of daemon.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-16.
-
Running one’s own root Certificate Authority in 2023
I made a web server / microservices thing that issues certs for clients from a CA root it automatically generates. Then internal reverse proxy connections use that cert so the whole path is TLD encrypted with full cert validation.
https://github.com/fsmv/daemon
- Show HN: A web server for using TLS with many back end servers
certificates
Posts with mentions or reviews of certificates.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-04.
-
You shouldn't run NSA-grade Wi-Fi at home
You can roll your own with https://github.com/smallstep/certificates. We maintain major open source projects and contribute a lot to other projects. I don’t think that means everything we do has to be open source. Sorry this one wasn’t. Doing this in pure open source would be a book, not a blog post.
Love Let’s Encrypt — we’re sponsors — but using them for WiFi is a terrible idea. You need internal PKI for WiFi.
- Running one’s own root Certificate Authority in 2023
-
Distributing ACME Let'sEncrypt certs for homelab
letsencrypt was always about moving the public internet off of http, it doesn't really make sense to use it throughout your internal network. but if you really want TLS and ACME for auto renewal, other solutions are available: https://github.com/smallstep/certificates
-
SSH With SSO
You could try step-ca: https://github.com/smallstep/certificates. There’s an OIDC provisioner for SSO and you can sign (short-lived) SSH certificates with it.
-
Web application to manage self-signed certificate authorities/certificates/keys
You could also check out out Step CA: https://github.com/smallstep/certificates and the accompanying CLI. It has an ACME server and other methods for requesting certificates. It can work/integrate with your existing root(s), too.
- Selfhosted CA tutorial
-
ACME setup. Domain required?
This is a lot more complicated setup but it works for me. I run a private CA called step-ca from smallstep and it provides CA and ACME endpoint. I use a .home domain. The trick is the validation for non-http devices which is typically the DNS-01 challenge. For this, I have unbound in pfsense setup to work with acme-dns so I can keep everything internal. Again its complicated but if your learning cyber security it might help get a handle on all things TLS. Btw way behind the scenes I think the ACME plugin is really just running acme.sh bash script which is really good. Final reminder as other have stated. Private CA is great but you need to distro the roots and intermediates out to your clients for trust. If all your trying to do is have an https web gui for pfsense from one device its pretty easy.
-
A convert from Judaism to Catholicism goes to r/Catholicism to ask if it would be appropriate to pass down a century old Jewish prayer shawl to his son. Not everyone is welcoming.
Just a little heads up https://smallstep.com/certificates/
-
Looking for an open source certificate management solution.
Step-ca: Not web based, but the CLI is pretty user friendly: https://smallstep.com/certificates/
-
Using k8s-apiserver as AAA server for microservices?
I was just looking at https://smallstep.com/certificates a few days ago. It looks like they have an operator that fits your description as well as example docs for setting up inter-microservice mtls.
What are some alternatives?
When comparing daemon and certificates you can also consider the following projects:
lego - Let's Encrypt/ACME client and library written in Go
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
bettertls - BetterTLS: A Name Constraints test suite for HTTPS clients.
boulder - An ACME-based certificate authority, written in Go.
easy-rsa - easy-rsa - Simple shell based CA utility
omgwtfssl - SSL certificate generation for developers who don't TLS good
rgca - Experiment in SSL CA management.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
traefik-certs-dumper - Dump ACME data from Traefik to certificates