Hal Murray via devel writes:
> I was trying to suggest using web browser to contact a few non NTS sites as
> a
> way to check the local collection of root certificates.
Web browsers often don't use the certificate chain of the system they're
running on. I generally use either use the gnutls to
watsonbl...@gmail.com said:
> The web server uses a different certificate from the time service, so
> connecting to 443 is no guarantee 1234 will work.
Good point. Thanks.
I was trying to suggest using web browser to contact a few non NTS sites as a
way to check the local collection of root
Merge Request submitted.
--
Sanjeev Gupta
+65 98551208 http://www.linkedin.com/in/ghane
On Tue, Dec 10, 2019 at 10:13 AM Sanjeev Gupta wrote:
> I will do that, and re-read Quick-NTS (which was written early on).
>
> --
> Sanjeev Gupta
> +65 98551208 http://www.linkedin.com/in/ghane
>
Hal Murray via devel writes:
> It seemed like a simplle/clean edit. I wonder what I missed.
My admonition some time ago that this is more complicated than you
seemed to think? In a strange way I'm relieved it blows up so quickly,
though.
You would really need to set up a testing rig that can sh
On Mon, Dec 9, 2019, 9:47 PM Hal Murray via devel wrote:
>
> > I also might have a local issue as I get:
> > NTSc: certificate invalid: 20=>unable to get local issuer certificate
> > (for the other servers mentioned at the howto page)
>
> What OS/distro/version are you using?
>
> Do you have the
All the packets go in and out, but the result is a crappy time server.
It seemed like a simplle/clean edit. I wonder what I missed.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/li
