Skip to content
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

Problem upgrading ZAP on linux and Windows #188

Closed
zapbot opened this issue Jun 4, 2015 · 8 comments
Closed

Problem upgrading ZAP on linux and Windows #188

zapbot opened this issue Jun 4, 2015 · 8 comments

Comments

@zapbot
Copy link
Contributor

zapbot commented Jun 4, 2015


Unable to upgrade config file /home/user/.ZAP/config.xml xml/config.old (Permission
denied)
java.io.FileNotFoundException: xml/config.old (Permission denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:145)
    at org.parosproxy.paros.model.FileCopier.copyLegacy(Unknown Source)
    at org.parosproxy.paros.model.FileCopier.copy(Unknown Source)
    at org.parosproxy.paros.Constant.initializeFilesAndDirectories(Unknown Source)
    at org.parosproxy.paros.Constant.<init>(Unknown Source)
    at org.parosproxy.paros.Constant.getInstance(Unknown Source)
    at org.zaproxy.zap.ZAP.main(Unknown Source)

This is when ZAP in installed in /usr/share/zaproxy so the user doesnt have write access.

Original issue reported on code.google.com by psiinon on 2011-10-03 20:28:00

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

Patched jar attached - please see if this fixes the problem

Original issue reported on code.google.com by psiinon on 2011-10-03 20:28:55

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

Issue 189 has been merged into this issue.

Original issue reported on code.google.com by psiinon on 2011-10-05 21:04:42

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

(No text was entered with this change)

Original issue reported on code.google.com by psiinon on 2011-10-05 21:05:45

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

I was having the same issue.
Patched zap.jar solves the issue. 
Please can you modify the zap.sh in the upstream package so it would be possible to
use it with shared installation out of the box?

I am using symbolic link to the zap base directory:
ln -s /opt/ZAP_1.3.3/zap.sh /usr/bin/zap

And modified zap.sh script to follow the symbolic link to the real directory:
#!/bin/sh
#Dereference from link to the real directory
SCRIPTNAME=$0
while [ -L "$SCRIPTNAME" ] ; do 
    SCRIPTNAME=`ls -l "$SCRIPTNAME" | awk ' { print $NF }'`
done

BASEDIR=`dirname $SCRIPTNAME`
cd "$BASEDIR"

java -jar zap.jar org.zaproxy.zap.ZAP $*

Original issue reported on code.google.com by michal.ambroz on 2011-10-18 14:02:36

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

Issue 211 has been merged into this issue.

Original issue reported on code.google.com by psiinon on 2011-10-27 07:18:12

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

(No text was entered with this change)

Original issue reported on code.google.com by psiinon on 2011-11-06 11:56:44

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

Tested 1.3.4 on Fedora16, works fine. 
Thank you

Original issue reported on code.google.com by michal.ambroz on 2011-11-07 19:27:26

@lock
Copy link

lock bot commented Nov 1, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Nov 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

1 participant