Frédéric L. W. Meunier
Sat Dec 27 03:23:00 GMT 2003
On Fri, 26 Dec 2003, Harold L Hunt II wrote:
> I think I reproduced it. But the screen updating is broken under all
> shells... not just cmd. For example, under bash, the "Resolving host"
> (or whatever it says) is left on the screen after the page loads, one
> line above the status bar. That is not correct; that line is supposed
> to be cleared from the screen, but it is staying in place. ELinks is
> just like links on Cygwin: it barely works :) I'm sure that someone
> that is interested could figure out what the problem is. It could be as
> simple as improper detection of the screen size.
By cmd.exe I meant using the default terminal with bash.
> >>--enable-local-cgi doesn't seem necessary, does it? The others seem
> >>valid to me and I will add them to the build script.
> > What do you mean by not necessary ? It's a feature, listed in
> > NEWS and enabled in contrib/elinks.spec.in, so may be worth.
> Tell me what it does. I thought I saw something that said it could
> cause a security hole. Plus, are local CGIs even an issue on Cygwin?
> Can we verify that the feature actually has something to work with?
> That is what I mean by not necessary: enabling it may have absolutely no
> benefit if the other pieces of the puzzle are not there on Cygwin.
I guess it does the same as in Lynx, allowing you to run local
CGIs without a web server.
I don't see any security issues. It adds 2 options which need
to be configured.
Protocols -> Local files -> Local CGI:
Allow local CGI (disabled by default)
Path (not set)
How to contact me - http://www.pervalidus.net/contact.html
More information about the Cygwin-apps