On Sun, Oct 07, 2018 at 11:00:48AM +0200, Andrej Shadura wrote:
>
> I’m unsure what can be done to help resolve this issue from the wpa side.
The only thing I can think of is that wpa could add a way to
specify the minimum tls version.
On Sun, Oct 07, 2018 at 11:00:48AM +0200, Andrej Shadura wrote:
> I’m unsure what can be done to help resolve this issue from the wpa side.
For debugging purposes, I'd still be interested to know this:
> On Wed, 5 Sep 2018 14:57:59 -0700 Josh Triplett
> wrote:
> > Is there a way I can easily get
On Wed, 5 Sep 2018 14:57:59 -0700 Josh Triplett
wrote:
> On Wed, Sep 05, 2018 at 11:48:56PM +0200, Kurt Roeckx wrote:
> > The problem here is that the CA you're connecting to has an
> > insecure certificate. You should talk to your administrator
> > to generate stronger keys.
>
> I am aware of th
On Wed, Sep 05, 2018 at 11:48:56PM +0200, Kurt Roeckx wrote:
> The problem here is that the CA you're connecting to has an
> insecure certificate. You should talk to your administrator
> to generate stronger keys.
I am aware of this, and I'm in the process of doing so.
> The "ca md too weak" is b
The problem here is that the CA you're connecting to has an
insecure certificate. You should talk to your administrator
to generate stronger keys.
The "ca md too weak" is because the certificate is probably using
SHA-1, while it should move to SHA256.
This can be worked around by using this in yo
5 matches
Mail list logo