Just want simple TLS for your .internal network?

• internal-contstrained-pki

  1 528 3.2 Shell

  Safely shareable TLS root CA for .internal networks using Name Constraints

• CodeRabbit

  coderabbit.ai featured

  CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

  

• mkcert

  137 51,171 1.9 Go

  A simple zero-config tool to make locally trusted development certificates with any names you'd like.

  mkcert might be getting this as well: https://github.com/FiloSottile/mkcert/pull/309/commits/92215... (this is linked from the current submission's readme)

• cert-manager

  111 12,237 9.7 Go

  Automatically provision and manage TLS certificates in Kubernetes

  

• Caddy

  423 59,028 9.5 Go

  Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS

  

  Not OP but I have a couple of implementations: one using caddyserver[0] as a reverse proxy in a docker-compose set up, and the other is a Kubernetes cluster using cert-manager[1].

  [0] https://caddyserver.com/

• bettertls

  4 166 5.3 Go

  BetterTLS: A Name Constraints test suite for HTTPS clients.

  

  A word of warning, client side support of name constraints may still be incomplete. I know it works on modern Firefox and Chrome, but there's lots of other software that uses HTTPS.

  This repo links to BetterTLS, which previously audited name constraint support, but BetterTLS only checked name constraint support at the intermediary certificates not at the trust anchors. I reported[1] the oversight a year back, but Netflix hasn't re-engineered the tests.

  Knowing how widely adopted name constraints are on the client side would be really useful, but I haven't seen a caniuse style analysis.

  Personally, I think the public CA route is better and I built a site that explores this[2].

  [1] https://github.com/Netflix/bettertls/issues/19

  [2] https://www.getlocalcert.net/

• acme.sh

  285 40,156 9.3 Shell

  A pure Unix shell script implementing ACME client protocol

  

  I use Dynu.com as my DNS provider (they're cheap, provide APIs and very fast to update which is great for home IP addresses that may change). Then, to get the certificates, I use https://github.com/acmesh-official/acme.sh which is a shell script. Copying the certificates to the relevant machines is done by a BASH script that runs the relevant acme.sh commands.

• Invidious

  429 16,506 9.6 Crystal

  Invidious is an alternative front-end to YouTube

  

  I'm looking for an answer to that. https://invidious.io/ looks like what I want, but I haven't tried it to see.

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

• certificates

  42 6,857 9.6 Go

  🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.

  

  How does this compare with smallstep step-ca certificates?

  https://github.com/smallstep/certificates

Suggest a related project