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

Already on GitHub? Sign in to your account

Zenmap crashes with Permission Denied on zenmap.conf #449

dmiller-nmap opened this Issue Jul 6, 2016 · 2 comments


None yet
2 participants

dmiller-nmap commented Jul 6, 2016 edited

This is reported too often to be a simple file permissions issue. It is probably a concurrency problem with opening, reading, and writing the config file. It started happening after we merged #247 and then fixed some other concurrency issues (r35718, r35721, r35726, r35727, r35744, specifically 97b5aa2).

Example reports:

@dmiller-nmap dmiller-nmap added this to the Release 2016-A milestone Jul 6, 2016

tremblerz added a commit to tremblerz/nmap that referenced this issue Jul 20, 2016

tremblerz added a commit to tremblerz/nmap that referenced this issue Jul 21, 2016

sergeykhegay added a commit to sergeykhegay/nmap that referenced this issue Jul 27, 2016

@dmiller-nmap Is this issue fixed..?

batrick pushed a commit to batrick/nmap that referenced this issue Aug 2, 2016

Simplify config reading/writing. Related #449
git-svn-id: https://svn.nmap.org/nmap@35970 e0a8ed71-7df4-0310-8962-fdc924857419

@dmiller-nmap dmiller-nmap reopened this Aug 30, 2016

For some reason, the user's zenmap.conf is being changed to read-only. I can't figure out where it's happening, so we'll just have to catch the appropriate error and suggest that the user go and fix it. I think it's not going to happen again, but I guess we'll see.

@nmap-bot nmap-bot closed this in fd37e97 Aug 31, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment