mkcert
minica
mkcert | minica | |
---|---|---|
132 | 10 | |
45,821 | 2,898 | |
- | - | |
2.7 | 3.0 | |
17 days ago | 7 days ago | |
Go | Go | |
BSD 3-clause "New" or "Revised" 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.
mkcert
-
HTTPS on Localhost with Next.js
The experimental HTTPS flag relies on mkcert, designed for a single development system. If you run a Docker container, the flag won’t configure your local browser to trust its certificate.
- Mkcert: Simple zero-config tool to make locally trusted development certificates
- Mkcert: Simple tool to make locally trusted dev certificates names you'd like
-
You Can't Follow Me
The author mentions difficulties with HTTPS and trying stuff locally.
I've had some success with mkcert [1] to easily create certificates trusted by browsers, I can suggest to look into this. You are your own root CA, I think it can work without an internet connection.
[1] https://github.com/FiloSottile/mkcert/
- SSL Certificates for Home Network
-
Simplifying Localhost HTTPS Setup with mkcert and stunnel
Solution: mkcert – Your Zero-Configuration HTTPS Enabler Meet mkcert, a user-friendly, zero-configuration tool designed for creating locally-trusted development certificates. Find it on its GitHub page and follow the instructions tailored for your operating system. For Mac users employing Homebrew, simply execute the following commands in your terminal:
-
10 reasons you should quit your HTTP client
Well, Certifi does not ship with your company's certificates! So requesting internal services may come with additional painful extra steps! Also for a local development environment that uses mkcert for example!
-
Show HN: Anchor – developer-friendly private CAs for internal TLS
My project, getlocalcert.net[1] may be the one you're thinking of.
Since I'm also building in this space, I'll give my perspective. Local certificate generation is complicated. If you spend the time, you can figure it out, but it's begging for a simpler solution. You can use tools like mkcert[2] for anything that's local to your machine. However, if you're already using ACME in production, maybe you'd prefer to use ACME locally? I think that's what Anchor offers, a unified approach.
There's a couple references in the Anchor blog about solving the distribution problem by building better tooling[3]. I'm eager to learn more, that's a tough nut to crack. My theory for getlocalcert is that the distribution problem is too difficult (for me) to solve, so I layer the tool on top of Let's Encrypt certificates instead. The end result for both tools is a trusted TLS certificate issued via ACME automation.
1. https://news.ycombinator.com/item?id=36674224
2. https://github.com/FiloSottile/mkcert
3. https://blog.anchor.dev/the-acme-gap-introducing-anchor-part...
-
Running one’s own root Certificate Authority in 2023
Looks like step-ca/step-cli [1] and mkcert [2] have been mentioned. Another related tool is XCA [3] - a gui tool to manage CAs and server/client TLS certificates. It takes off some of the tedium in using openssl cli directly. It also stores the certs and keys in an encrypted database. It doesn't solve the problem of getting the root CA certificate into the system store or of hosting the revocation list. I use XCA to create and store the root CA. Intermediate CAs signed with it are passed to other issuers like vault and step-issuer.
[1] https://smallstep.com/docs/step-ca/
[2] https://github.com/FiloSottile/mkcert
[3] https://hohnstaedt.de/xca/
-
Show HN: Local development with .local domains and HTTPS
We use mkcert for this, it works wonderfully.
https://github.com/FiloSottile/mkcert
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?
nginx-docker-ssl-proxy - A docker way to access localhost:8081 from https://local.dev
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.
certificates - 🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
community.hashi_vault - Ansible collection for managing and working with HashiCorp Vault.
gosumemory - Cross-Platform memory reader for osu!
bettertls - BetterTLS: A Name Constraints test suite for HTTPS clients.
rustls - A modern TLS library in Rust
caddy-docker-proxy - Caddy as a reverse proxy for Docker
uvicorn - An ASGI web server, for Python. 🦄
homelab.express
WSL - Issues found on WSL
rfc2136_bridge