Skip to content

Dillo browser's https not working when non-absolute path for confgfile used #256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
crass opened this issue Sep 1, 2018 · 0 comments
Open

Comments

@crass
Copy link

crass commented 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 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.

crass pushed a commit to crass/proxychains-ng that referenced this issue Sep 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant