mirror of
https://github.com/rkd77/elinks.git
synced 2025-05-18 00:48:57 -04:00
a6966e9472
Currently, when ELinks passes the name of a local file to an external MIME handler program, it encodes the name as a URI. Programs typically do not expect this, and they then fail to open the file. ELinks should instead quote the file name for the shell. Unfortunately, Debian has lines like this in /etc/mailcap: audio/mpeg; xmms '%s'; test=test "$DISPLAY" != "" If ELinks were changed to replace the %s with e.g. '/home/Kalle/doc/Topfield/How to upgraded the Firmware(English).pdf' (quotes included), then the quotes would cancel out and the shell would split the file name into multiple arguments. That could even provide a way for malicious persons to make ELinks run arbitrary shell commands. The examples in RFC 1524 all have %s without any quotes. Debian has two bug reports about the quoting behaviour: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90483 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=221717 This patch therefore tries to detect whether the %s has been quoted already, and remove the quotes if so. That way, the next patch will be able to safely add its own quotes. This removal of quotes applies only to mailcap files; MIME handlers defined in elinks.conf should already be in the format preferred by ELinks. (The patch was attachment 438 of bug 991, by Witold Filipczyk. This commit message was written by Kalle Olavi Niemitalo.)
ELinks - an advanced web browser ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ELinks is an advanced and well-established feature-rich text mode web (HTTP/FTP/..) browser. ELinks can render both frames and tables, is highly customizable and can be extended via scripts. It is very portable and runs on a variety of platforms. The ELinks official website is available at http://elinks.cz/ Please see the SITES file for mirrors or other recommended sites. If you want to install ELinks on your computer, see the INSTALL file for further instructions. A good start point is documentation files available in doc/, especially the file named index.txt. If you want to request features or report bugs, see community information at http://elinks.cz/community.html and feedback information available at http://elinks.cz/feedback.html. If you want to write some patches, please first read the doc/hacking.txt document. If you want to add a new language or update the translation for an existing one, please read po/README document. If you want to write some documentation, well, you're welcome! ;) Historical notes ~~~~~~~~~~~~~~~~ Initially, ELinks was a development version of Links (Lynx-like text WWW browser), with more liberal features policy and development style. Its purpose was to provide an alternative to Links, and to test and tune various new features, but still provide good rock-solid releases inside stable branches. Why not contribute to Links instead? Well, first I made a bunch of patches for the original Links, but Mikulas wasn't around to integrate them, so I started releasing my fork. When he came back, a significant number of them got refused because Mikulas did not like them, as he just wouldn't have any use for them himself. He wants to keep Links with a relatively closed feature set and merge only new features which he himself needs. It has advantages that the tree is very narrow and the code is small and contains very little bloat. ELinks, on the contrary, aims to provide a full-featured web browser, superior to both lynx and w3m and with the power (but not slowness and memory usage) of Mozilla, Konqueror and similar browsers. However, to prevent drastic bloating of the code, the development is driven in the course of modularization and separation of add-on modules (like cookies, bookmarks, ssl, scripting etc). For more details about ELinks history, please see http://elinks.cz/history.html If you are more interested in the history and various Links clones and versions, you can examine the website at http://links.sf.net/ vim: textwidth=80