You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suppose you have a configfile in the current working directory. The following command will fail to load the https url in the dillo web browser (you must also make sure that there are no implicitly searched for configfiles also).
The reason is that dillo does a chdir to /tmp and then forks a "server" process. This forking causes the dll to initialize for the new process, which will eventually call get_config_path. However, since the cwd is now /tmp, get_config_path will not find a configfile and exit the process. Dillo will not be able to communicate with the (dead) server, so it won't be able to load the https url.
I believe a good fix would be to have get_config_path set the configfile envvar to the realpath of the used configfile.
The text was updated successfully, but these errors were encountered:
crass
pushed a commit
to crass/proxychains-ng
that referenced
this issue
Sep 1, 2018
Suppose you have a configfile in the current working directory. The following command will fail to load the https url in the dillo web browser (you must also make sure that there are no implicitly searched for configfiles also).
proxychains4 -f proxychains.conf dillo https://api.ipify.org
The reason is that dillo does a chdir to
/tmp
and then forks a "server" process. This forking causes the dll to initialize for the new process, which will eventually callget_config_path
. However, since the cwd is now/tmp
,get_config_path
will not find a configfile andexit
the process. Dillo will not be able to communicate with the (dead) server, so it won't be able to load thehttps
url.I believe a good fix would be to have
get_config_path
set the configfile envvar to therealpath
of the used configfile.The text was updated successfully, but these errors were encountered: