Regarding the first question, no, I don't think this is the intended behavior.
No matter which site I access with https protocol, I now get this message with
Lynx (and did not previously). I do not get any indication of ssl problems when
accessing the same sites with any other browser. Example sites are
https://www.google.com and https://mail.yahoo.com. But, to answer one of your
other questions, yes, I have built on Linux as well and don't have this problem
there. But that is immaterial - either Lynx with SSL should work with Cygwin
(in which case this might indicate a problem that needs addressing) or it
shouldn't (in which case perhaps some sort of disclaimer is needed). In either
case, I was just hoping to supply some extra diagnostic information which might
lead to an understanding of why this problem might come up, or how it might be
solved.
________________________________
From: "[email protected]" <[email protected]>
To: [email protected]
Sent: Monday, April 8, 2013 9:00 AM
Subject: Lynx-dev Digest, Vol 111, Issue 5
Send Lynx-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.nongnu.org/mailman/listinfo/lynx-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lynx-dev digest..."
Today's Topics:
1. Re: Lynx-dev Digest, Vol 111, Issue 4 (Supriyo Biswas)
----------------------------------------------------------------------
Message: 1
Date: Sun, 07 Apr 2013 22:41:41 +0530
From: Supriyo Biswas <[email protected]>
To: [email protected]
Subject: Re: [Lynx-dev] Lynx-dev Digest, Vol 111, Issue 4
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 4/5/2013 9:30 PM, [email protected] wrote:
> Not that all is well with the successfully compiled version. Whenever I
> access a site with https now, I get a prompt: "SSL error: unable to get local
> issuer certificate - Continue?" This definitely did not happen in July when I
> built the image, but I cannot tell you when it did start. This also happens
> when I use the suggested workaround (define CRYPT etc.) with the current
> release.
Shouldn't this be the exact intended behaviour? Local certificates are
not installed, and every browser does have a list of certificates. Can
you try to build on Linux? It shouldn't happen there, since Linux
presumably should have a list of certificates that Lynx can use.
(Problems with network connectivity and incompatibility of USB modems
entirely prevent me from using Linux.)
> Finally, I noticed during this investigation that, if I try to build on
> Cygwin with ssl and don't have ssl installed on my system, configure and make
> nevertheless complete successfully (without ssl of course). I don't know if
> this is intended, but it seems wrong.
While I don't have much experience, some software is configured to
compile like that - if `configure' doesn't find the dependency it tries
to compile regardless of the option.
Regards,
------------------------------
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
End of Lynx-dev Digest, Vol 111, Issue 5
****************************************
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
