[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lynx-dev] SSL Common Name issue & Form Submissions in Lynx
From: |
Stefan Caunter |
Subject: |
Re: [Lynx-dev] SSL Common Name issue & Form Submissions in Lynx |
Date: |
Sun, 4 Dec 2016 20:18:53 -0500 |
irrelevant
your question is about certificates, not ssl implementation
lynx worked fine with eay ssl, before openssl, but the actual certificate
checks were not enforced until much later
please see the ssl.certs doc for instructions on certificate use with lynx
Sent from my iPhone
> On Dec 4, 2016, at 18:56, Matt Caswell <address@hidden> wrote:
>
>
>
>> On 04/12/16 01:46, Menasheh Peromsik wrote:
>> Hello Lynx developers,
>>
>> I recently used lynx for the automation of logging in to captive portal
>> wifis
>> <https://peromsik.com/blog/how-to-set-up-automatic-wifi-captive-portal-login/>
>> on
>> Windows 10.
>>
>> Because they seem to use https, I had to use the non-color version
>> supporting https through OpenSSL. (Aside: Why doesn't Google Chrome
>> have any issue using https out of the box? It doesn't need third party
>> stuff)
>>
>> I tried to install OpenSSL from the recommended page
>> <http://www.slproweb.com/products/Win32OpenSSL.html>, but the installers
>> for the most recent version seem to not be including the necessary
>> DLLs.
>
> Did you read this bit on the that page:
>
> "August 29, 2016 - OpenSSL 1.1.0 is quite different from previous
> releases. Developers need to recompile their software to support 1.1.0.
> Users should install BOTH the 1.0.2 series (LTS) and the 1.1.0 series
> for maximum application compatibility. "
>
> Matt
>
> _______________________________________________
> Lynx-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lynx-dev