Yo Hal! On Thu, 31 Jan 2019 17:28:38 -0800 Hal Murray via devel <devel@ntpsec.org> wrote:
> Gary said:
> > Not really. If you have a fixed public hostname, then Lets Encrypt
> > is easy and quick. If you do not have a fixed public hostname,
> > then game over.
>
> Let's encrypt says you need a domain rather than just a public
> hostname.
Nope, just a domain name (FQDN).
> > In order to get a certificate for your website's domain from Let's
> > Encrypt, you have to demonstrate control over the domain.
>
>
> Thanks, but I'm looking for a way to test without a domain.
Easy, just use a hostname *FQDN).
> Lots of
> people have more than one box at home. They should be able to test
> and experiment without getting a domain.
Can't get a TLS cert w/o a hostname (FQDN).
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpK1g5qIn61F.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
