From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH v2 backup 02/27] add dns alias schema
Date: Thu, 29 Apr 2021 09:12:19 +0200 [thread overview]
Message-ID: <20210429071219.l2ma4osf3o3xzclm@wobu-vie.proxmox.com> (raw)
In-Reply-To: <1626464218.1336.1619625327468@webmail.proxmox.com>
On Wed, Apr 28, 2021 at 05:55:27PM +0200, Dietmar Maurer wrote:
> Is this the same syntax used for DNS SRV records?
>
> https://en.wikipedia.org/wiki/SRV_record
Disclaimer: My main motivation was, I just followed along with what
we're doing in PVE (and did the same in PMG as well).
TBH I don't know if any ACME implementation worries about that at all.
The main idea is this:
* you want to get a certificate for foo.bar.com
* giving pbs direct access to managing the `foo.bar.com` or `bar.com`
zones is inconvenient or impossible
* you setup a `CNAME` for `_acme-challenge.foo.bar.com` to point to
X.Y.Z
* you configure the domain foo.bar.com and set the alias to X.Y.Z, so
that our DNS plugins will set the TXT entry for X.Y.Z instead of
`_acme-challenge.foo.bar.comm`
* the ACME provider's DNS resolver will decide which values for X, Y
and Z they're willing to accept while resolving the TXT entry.
Most likely they can be completely arbitrary. We know that due to
common practice, they'll most likely allow at least hostnames with
the addition of leading underscores, but as far as formal
definitions go, the DNS RFC is the only "real source of
what-should-be-the-truth", while in practice you'll just have to try
and see if it works...
And sure, *technically* we could just relax the DNS schema in general,
but then user's may run into issues when they configure something that
should be legal as per the DNS RFC but is not accepted by their browsers
or some other tool. Of course we could still relax it and just keep the
"normal" restrictions purely in the GUI... I don't know.
next prev parent reply other threads:[~2021-04-29 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 15:55 Dietmar Maurer
2021-04-29 7:12 ` Wolfgang Bumiller [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-28 18:18 Dietmar Maurer
2021-04-29 6:51 ` Wolfgang Bumiller
2021-04-28 16:10 Dietmar Maurer
2021-04-28 16:34 ` Thomas Lamprecht
2021-04-28 11:15 Dietmar Maurer
2021-04-28 11:42 ` Wolfgang Bumiller
2021-04-22 14:01 [pbs-devel] [PATCH v2 backup 00/27] Implements ACME support for PBS Wolfgang Bumiller
2021-04-22 14:01 ` [pbs-devel] [PATCH v2 backup 02/27] add dns alias schema Wolfgang Bumiller
2021-04-28 10:26 ` Dietmar Maurer
2021-04-28 11:07 ` Wolfgang Bumiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210429071219.l2ma4osf3o3xzclm@wobu-vie.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox