daemon
cfssl
| daemon | cfssl | |
|---|---|---|
| 2 | 24 | |
| 11 | 8,493 | |
| - | 1.0% | |
| 8.3 | 7.5 | |
| 4 months ago | 5 days ago | |
| Go | Go | |
| MIT License | BSD 2-clause "Simplified" 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.
daemon
-
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
cfssl
- Running one’s own root Certificate Authority in 2023
- Selfhosted CA tutorial
-
i must be the only guy that understands certificates
cfssl is kinda outright better version of that.
-
SSL certificate problem: unhandled critical extension
The Cloudflare SSL tools at https://github.com/cloudflare/cfssl might help. Here's what it shows for one of the example Snake Oil certs:
-
Private CA management
I've used this in the past and it worked great. https://github.com/cloudflare/cfssl
- Linux Certificate Authority root stores have a too simple view of 'trust'
- Creating an internal Certificate Authority in 2022 that is accepted by modern web browsers.
-
How to create users in Kubernetes
The first step is to create the source key that represents our user. This key is created using a tool like openssl but another popular tool to use is cfssl, created by Cloudflare. Some folks think cfssl is easier to use, and it definitely looks easier to script. But for this example we will use openssl. You can also choose to create the key using a number of different algorithms. For this example we will use ED25519.
-
[Legal notice] IoT Core will be discontinued on Aug. 16, 2023
TLS/SSL worked well with client certificates generated by the CFSSL API.
-
Feedback on a Self-signed SSL CA?
Not sure if relevant but we used tooling from CloudFlare in the past: https://github.com/cloudflare/cfssl
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.
OpenSSL - TLS/SSL and crypto library
lego - Let's Encrypt/ACME client and library written in Go
easy-rsa - easy-rsa - Simple shell based CA utility
bettertls - BetterTLS: A Name Constraints test suite for HTTPS clients.
LetsEncrypt-PRTG - Post request script to install an SSL certificate obtained with Certify the Web or win-acme in PRTG.
acme.sh - A pure Unix shell script implementing ACME client protocol
rgca - Experiment in SSL CA management.
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.