On Wed, Apr 11, 2018 at 02:39:52PM -0500, Jonathan Bennett wrote:
> On 04/11/2018 02:29 PM, Jonathan Bennett wrote:
> > Ah, that's what it is. Firefox is pulling Comodo off their CA list, and
> > that's who signs Cipherdyne's cert. I'm sure Michael will get this sorted
> > on the server end as
On 04/11/2018 02:29 PM, Jonathan Bennett wrote:
> Ah, that's what it is. Firefox is pulling Comodo off their CA list, and
> that's who signs Cipherdyne's cert. I'm sure Michael will get this sorted on
> the server end as soon as he can.
I may have jumped the gun on this conclusion. The article
Ah, that's what it is. Firefox is pulling Comodo off their CA list, and that's
who signs Cipherdyne's cert. I'm sure Michael will get this sorted on the
server end as soon as he can.
On 04/11/2018 02:19 PM, Mattia Oss wrote:
> On Wed, Apr 11, 2018 at 12:48:38PM -0500, Jonathan Bennett wrote:
>
On Wed, Apr 11, 2018 at 12:48:38PM -0500, Jonathan Bennett wrote:
> Is it only the cipherdyne site that gives that error, or all https sites?
> It's probably a sign that your CA file isn't in place as wget expects. Is
> this from within a Cygwin instance on Windows, per chance? The following i
Is it only the cipherdyne site that gives that error, or all https sites? It's
probably a sign that your CA file isn't in place as wget expects. Is this from
within a Cygwin instance on Windows, per chance? The following is a link
describing what
I suspect to be happening.
https://stackoverfl
