News for hackers. Stuff that matters.
Re:Show HN: Make domain verification as easy as verifying an... by e12e on Friday May 05, 2023 @10:01AM (#35829299)
Wouldn't it be simpler to just build on the acme challenges?

https://letsencrypt.org/docs/challenge-types/

Re:Show HN: Make domain verification as easy as verifying an... by elliottinvent on Friday May 05, 2023 @10:04AM (#35829353)
DNS-01 is a standardisation of the same methods service providers have been using for well over a decade. Ok they've started using subdomains instead of the apex [1], but really it's more of the same.

This protocol offers additional functionality and less friction.

1. dig target.com TXT

Re:Show HN: Make domain verification as easy as verifying an... by e12e on Friday May 05, 2023 @10:07AM (#35829406)
> This protocol offers additional functionality and less friction.

Most users will be using letsencrypt anyway, so at a minimum this adds friction by forcing (most) users to implement two protocols?

Re:Show HN: Make domain verification as easy as verifying an... by elliottinvent on Friday May 05, 2023 @10:20AM (#35829586)
Do you mean LE or DNS-01?

DNS-01 is unique per service provider.

I don't think domain registrants care about protocols, they care about how many things they've got to do with their DNS.

With DNS-01 and older methods it was based on, there's friction for each service provider. With the Domain Verification protocol there's friction first time only.

Sorry if I've misunderstood something here. If so, please forgive me and elaborate to help me understand.

Re:Show HN: Make domain verification as easy as verifying an... by e12e on Friday May 05, 2023 @10:33AM (#35829741)
As a user of LE, you need to implement http or DNS (or tls) challenge - typically via a tool that takes a pointer to your provider (letsencrypt).

I claim that it would be less friction to simply use the same tool for verifying domain control (suplly facebook as the provider).

Ed: although thinking about it, existing tools for interfacing with LE probably do too much (create certificate requests) - so might not make that much sense to reuse the tools/clients as is.