Bug#953974: ITP: mkcert -- A simple zero-config tool to make locally trusted development certificates with any names you'd like.
Hi Aloïs
Sorry, I haven't looked at this in ages, my need for this disappeared
soon after I started looking at packaging (this should probably be
moved to RFP).
>From what I recall, there was only one dependency that needed to be
packaged, but there was some odd name-mangling going on, and not being
that familiar with packaging go libs, I stopped at that point. If you
want to package it, go ahead.
Regards
James
On Sun, 7 Nov 2021 at 21:25, Aloïs Micard <creekorful@debian.org> wrote:
>
> Hello there!
>
> I'm greatly interested about mkcert packaging, have you done any progress?
> Do you need sponsoring?
>
> Cheers,
>
> On Sun, 15 Mar 2020 19:29:57 +1100 James Tocknell <aragilar@gmail.com> wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: James Tocknell <aragilar@gmail.com>
> >
> > * Package name : mkcert
> > Version : 1.4.1-1
> > Upstream Author : Filippo Valsorda
> > * URL : https://github.com/FiloSottile/mkcert
> > * License : BSD-3-clause
> > Programming Lang: Go
> > Description : A simple zero-config tool to make locally trusted
> > development certificates with any names you'd like.
> >
> > mkcert mkcert is a simple tool for making locally-trusted development
> > certificates. It requires no configuration.
> > .
> > ``` $ mkcert -install Created a new local CA at
> > "/Users/filippo/Library/Application Support/mkcert" 💥 The local CA
> > is now installed in the system trust store! ⚡️ The local CA is now
> > installed in the Firefox trust store (requires browser restart)! 🦊
> > .
> > $ mkcert example.com "*.example.com" example.test localhost 127.0.0.1 ::1
> > Using the local CA at "/Users/filippo/Library/Application Support/mkcert"
> > ✨
> > .
> > Created a new certificate valid for the following names 📜
> > - "example.com" - "*.example.com" - "example.test" - "localhost" -
> > "127.0.0.1" - "::1"
> > .
> > The certificate is at "./example.com+5.pem"
> > and the key at "./example.com+5-key.pem" ✅ ``` <p
> > align="center"><img width="498" alt="Chrome and Firefox screenshot"
> > src="
> > https://user-images.githubusercontent.com/1225294/51066373-96d4aa80-15be-11e9-91e2-f4e44a3a4458.png
> > "></p>
> > Using certificates from real certificate authorities (CAs) for development
> > can be dangerous or impossible (for hosts like example.test, localhost
> > or 127.0.0.1), but self-signed certificates cause trust errors. Managing
> > your own CA is the best solution, but usually involves arcane commands,
> > specialized knowledge and manual steps.
> > .
> > mkcert automatically creates and installs a local CA in the system
> > root store, and generates locally-trusted certificates. mkcert does
> > not automatically configure servers to use the certificates, though,
> > that's up to you. Installation Warning: the rootCA-key.pem file that
> > mkcert automatically generates gives complete power to intercept secure
> > requests from your machine. Do not share it. macOS On macOS, use Homebrew
> > (https://brew.sh/)
> > .
> > .
> > brew install mkcert brew install nss # if you use Firefox
> > .
> > .
> > or MacPorts (https://www.macports.org/).
> > .
> > .
> > sudo port selfupdate sudo port install mkcert sudo port install nss #
> > if you use Firefox
> > .
> > Linux On Linux, first install certutil.
>
> --
> Aloïs Micard <creekorful@debian.org>
>
> GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
>
--
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.).
It isn't good enough for Tim Berners-Lee, and it isn't good enough for
me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.
Truly great madness cannot be achieved without significant intelligence.
- Henrik Tikkanen
If you're not messing with your sanity, you're not having fun.
- James Tocknell
In theory, there is no difference between theory and practice; In
practice, there is.
Reply to: