[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] Debian Port of Lynx and SSL

From: Thomas Dickey
Subject: Re: [Lynx-dev] Debian Port of Lynx and SSL
Date: Mon, 2 Jan 2006 16:06:42 -0500 (EST)

On Mon, 2 Jan 2006, Martin McCormick wrote:

        I have Lynx Version 2.8.5rel.1 (04 Feb 2004)
libwww-FM 2.14, SSL-MM 1.4.1, OpenSSL 0.9.6g
Built on freebsd4.7 Nov 19 2005 16:33:26

        and it handles a local lynx.cfg file directive of
correctly in that SSL sites now just work like they used to before the
increased security.

        On a Debian system, I have the most recent lynx port installed which is

Lynx Version 2.8.6dev.11 (05 Jan 2005)

lynx-cur is 2.8.6dev.16 (though that shouldn't make much difference here -
a quick look at the changelog doesn't show me that there are any changes to this feature since 2.8.5rel.1).

libwww-FM 2.14, SSL-MM 1.4.1, GNUTLS 1.0.16, ncurses 5.4.20040208
Built on linux-gnu Jan  6 2005 11:36:38

        It does not seem to understand

        It is as if one hadn't put it in the local lynx.cfg file at
all.  There is no error message, it just silently ignores it and acts
as if there was no directive at all.

But the -trace option of lynx would show if the data's being read.
The first thing I'd suggest is to ensure it's not a configuration
glitch (versus a bug).  If I do

        lynx -trace-mask=8 -trace .

and then look just at the lines in $HOME/Lynx.trace containing (ignoring case) "force_ssl_prompt", I see this

LYReadCFG ENABLE_LYNXRC:force_ssl_prompt:ON
enable_lynxrc(force_ssl_prompt) on
LYrcFile force_ssl_prompt:prompt

That tells me that my lynx.cfg sets it to "no", but it's overridden
by my .lynxrc file, which sets it to "prompt".

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]