rfc2136_bridge
minica
| rfc2136_bridge | minica | |
|---|---|---|
| 1 | 10 | |
| 4 | 2,920 | |
| - | - | |
| 1.4 | 3.0 | |
| about 1 year ago | 16 days ago | |
| Python | Go | |
| MIT License | 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.
rfc2136_bridge
-
Easy HTTPS for your private networks
Somewhat related - I made a bridge server [1] that lets ACME clients use standard RFC2136 to solve DNS-01 challenges for internal names without them needing credentials for the actual DNS backend (Route 53 in my case).
[1] https://github.com/schlarpc/rfc2136_bridge/blob/main/src/rfc...
minica
-
Easy HTTPS for your private networks
MiniCA[0] works for this, quite trivial to setup and stamp out certs.
[0] https://github.com/jsha/minica
-
How to create SSL certs for local domain?
I use minica (https://github.com/jsha/minica) for exactly that purpose. It’s a single binary that’s generating my Certificates easy enough.
-
Creating an internal Certificate Authority in 2022 that is accepted by modern web browsers.
I would personnally use minica if i had to manage a internal CA. But i don’t know if it can work with an intermediate certificate for signing.
-
The Illustrated QUIC Connection
I found minica very useful to do something like this (no affiliation): https://github.com/jsha/minica
-
HTTPS in local network
https://github.com/jsha/minica can be quite handy for this as it can generate wildcard certs as well as a root
-
SSL problems for internal network behind VPN with no access to Let'sEncrypt SSL method.
Other than that, there are some projects which help generating a self-signed chain with a root cert you could trust on the client machines. E.G. https://github.com/jsha/minica
-
Fast and easy way to setup web developer certificates
Before to generate local certificates I used minica.
-
Easy TLS without certificate authority?
You could use something like https://github.com/jsha/minica if the fact that it's golang doesn't bother you 😉
-
Looking for a new project, how do I prevent this when I access all my different LAN-base server GUIs?
If you’re just hosting locally and don’t feel like figuring out OpenSSL, easyRSA, etc etc, you can use minica to generate a wildcard cert signed by your own certificate authority. Then just add the root cert to all your devices and add the wildcard cert to any of the reverse proxies suggested on this post.
-
Build a tiny certificate authority for your homelab
https://github.com/jsha/minica has been around longer and has met all my home lab needs so far. It's even plugged on LetsEncrypt-- https://letsencrypt.org/docs/certificates-for-localhost.
What are some alternatives?
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
cert-manager - Automatically provision and manage TLS certificates in Kubernetes
docker-swag - Nginx webserver and reverse proxy with php support and a built-in Certbot (Let's Encrypt) client. It also contains fail2ban for intrusion prevention.
community.hashi_vault - Ansible collection for managing and working with HashiCorp Vault.
bettertls - BetterTLS: A Name Constraints test suite for HTTPS clients.
caddy-docker-proxy - Caddy as a reverse proxy for Docker
homelab.express
Ockam - Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit