mkcert
minica
Our great sponsors
mkcert | minica | |
---|---|---|
130 | 10 | |
45,338 | 2,869 | |
- | - | |
0.0 | 4.4 | |
23 days ago | 4 months 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
-
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.
-
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/
-
Show HN: Local development with .local domains and HTTPS
We use mkcert for this, it works wonderfully.
-
Implementing TLS in Kubernetes
mkcert: This is used to obtain a trusted TLS certificate with a custom domain name for your development machine. You can install mkcert on your development machine following the official instructions.
-
Easy HTTPS for your private networks
I've been pretty frustrated with how private CAs are supported. Your private root CA can be maliciously used to MITM every domain on the Internet, even though you intend to use it for only a couple domain names. Most people forget to set Name Constraints when they create these and many helper tools lack support [1][2]. Worse, browser support for Name Constraints has been slow [3] and support isn't well tracked [4]. Public CAs give you certificate transparency and you can subscribe to events to detect mis-issuance. Some hosted private CAs like AWS's offer logs [5], but DIY setups don't.
Even still, there are a lot of folks happily using private CAs, they aren't the target audience for this initial release.
[1] https://github.com/FiloSottile/mkcert/issues/302
[2] https://github.com/cert-manager/cert-manager/issues/3655
[3] https://alexsci.com/blog/name-non-constraint/
[4] https://github.com/Netflix/bettertls/issues/19
[5] https://docs.aws.amazon.com/privateca/latest/userguide/secur...
-
Quick Start: VS Code Setup for Kintone Customization Development
mkcert command-line tool that generates locally-trusted development certificates
-
uBlock (via EasyList) now blocks domains that resolve to localhost
> if you're developing software you should probably be running without any addons like uBlock enabled to prevent surprises in production for your non-uBlock users.
It seems to me there's a higher risk that uBlock blocks something and break something than uBlock making something work that wouldn't for people not having it. I once had a filter block something called /share/ or share.js, fortunately I noticed during the development.
> Besides that, you can't get HTTPS for these domains (without the mess of a custom CA and even then you'll run into CT issues)
Indeed. I recently had to do this and found mkcert [1] which makes it very easy to do. But it's overkill for most situations.
-
Managing local SSL certificates without port
As I like automation scripts, I have created a script to automate to create local certifications (supported by mkcert) and remove the PORT's from the url through a proxy with Docker image base on Nginx.
minica
-
Easy HTTPS for your private networks
MiniCA[0] works for this, quite trivial to setup and stamp out certs.
-
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
-
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
certificates - 🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
gosumemory - Cross-Platform memory reader for osu!
rustls - A modern TLS library in Rust
uvicorn - An ASGI web server, for Python. 🦄
WSL - Issues found on WSL
Next.js - The React Framework
ddev - Docker-based local PHP+Node.js web development environments
traefik-certs-dumper - Dump ACME data from Traefik to certificates
shopify-app-sveltekit
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.
tailscale-systray - Linux port of tailscale system tray menu.