[Bug 297301] [NEW PORT] devel/mkcert: simple tool for making locally-trusted development certificates
[email protected] Wed, 05 Aug 2026 17:57:18 +0000
| Newsgroups | gmane.os.freebsd.devel.ports.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D297301
Bug ID: 297301
Summary: [NEW PORT] devel/mkcert: simple tool for making
locally-trusted development certificates
Product: Ports & Packages
Version: Latest
Hardware: Any
URL: https://github.com/FiloSottile/mkcert
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: [email protected]
Reporter: [email protected]
Created attachment 273490
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D273490&action=
=3Dedit
Patch to add devel/mkcert v 1.4.4
Patch to add devel/mkcert v1.4.4
mkcert is a simple tool for making locally-trusted development certificates=
. It
requires no configuration.
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 sto=
re,
and generates locally-trusted certificates.
mkcert does not automatically configure servers to use the certificates,
though, that's up to you.
-----
One of the top installed homebrew packages, support for FreeBSD is provided=
by
this (open) PR: https://github.com/FiloSottile/mkcert/pull/552, I'm not sur=
e if
best practice is to to build from the fork, use remote patch files or just =
keep
the local implementation in the port (as I hope the PR will eventually get
merged). Thanks
--=20
You are receiving this mail because:
You are the assignee for the bug.=