bettertls

BetterTLS: A Name Constraints test suite for HTTPS clients. (by Netflix)

Bettertls Alternatives

Similar projects and alternatives to bettertls

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better bettertls alternative or higher similarity.

bettertls reviews and mentions

Posts with mentions or reviews of bettertls. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-01.
  • Show HN: Anchor – developer-friendly private CAs for internal TLS
    4 projects | news.ycombinator.com | 1 Nov 2023
    Have you done any research about how well different web clients support name constraints? I know that Chrome only recently started respecting Name Constraint on root CAs [1]. The BetterTLS project tracks a bunch of related concerns, but oddly missed this one [2]. I'm wary of this approach since I don't know if the various software I use will enforce it.

    1. https://alexsci.com/blog/name-non-constraint/

    2. https://github.com/Netflix/bettertls/issues/19

  • Running one’s own root Certificate Authority in 2023
    12 projects | news.ycombinator.com | 16 Sep 2023
    Wouldn't it be nice if LetsEncrypt could issue you a (1) name constrained, (2) 90-day limited intermediate CA with just the (3) DNS-01 challenge? I argue that such an intermediate CA would have no more authority than a wildcard cert which you can get today, so they should be able to issue it. [1] Everything supports name constraints now, which used to be an issue but isn't anymore.

    Then stick it in step-ca and issue all your certificates with internal ACME.

    This would solve a lot of problems, such as leaking private hostnames in the certificate transparency log, or hitting issuance rate limits on LE servers.

    [1]: https://news.ycombinator.com/item?id=29811552

    [2]: https://bettertls.com/

  • Easy HTTPS for your private networks
    13 projects | news.ycombinator.com | 10 Jul 2023
    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...

  • A note from our sponsor - InfluxDB
    www.influxdata.com | 8 May 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic bettertls repo stats
3
156
4.8
about 2 months ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com