I looked into the error you reported a bit more. What is happening
are some SVN conflicts due to changes in the OWASP ESAPI SwingSet
Interactive project (which I also had to make minor changes to in
order to get it to work on the VM). If you get past that, there are
also conflicts when the owaspbwa-update-all.sh script tries to update
WebGoat.NET from it's GIT repository.
Those update scripts are for "living on the edge" and are frequently
going to encounter these types of issues, especially as more time
passes after the release of a VM. You are also at the mercy of the
developers for the project you are updating... the code in their
repository may not be working (maybe they are in the middle of a
rewrite, for example). What I may do is add some prompts into that
script to allow the user to choose whether to update each component...
at least then if you find that one component is having issues, then
you could skip that one. Unfortunately, by the time you find out that
there is an issue, you've probably already broken that app since it
has partially updated and may no longer compile / run properly.
Fortunately, it is a VM so you can revert to an earlier state.
In the short term, I was able to get the script to work by skipping
the updates to those two components. That is, you can edit
/usr/local/bin/owaspbwa-update-all.sh and comment out (add a # to the
beginning of) the following two lines:
- Line 71 ("svn update /owaspbwa/owasp-esapi-java-swingset-interactive-svn")
- Line 81 ("git pull" under the update for
webgoat.net)
Once this above changes are made, then run owaspbwa-update-all.sh and
everything looks to run smoothly. At this point, however, it doesn't
appear that there are any updates to the other components, so this
doesn't gain you anything. If there are updates to something like
DVWA or WebGoat (for Java) before the next OWASPBWA release, though,
then this would get you those.
I included the GoatDroid item in the issues on Google Code as well:
https://code.google.com/p/owaspbwa/issues/detail?id=68. As far as I
know, there is not a server side component to GoatDroid at this time,
it is all code that runs on the device / emulator itself. If I'm
missing something, though, let me know. I'll continue to keep an eye
on that project.
I just looked at the similar iOS project iGoat. They do have a server
side component (written in Ruby). I've opened a new enhancement
request to include that on the VM.
Unfortunately I've got limited control over the stuff on SourceForge
and don't have an option to completely remove the trackers, etc. They
went through some significant upgrades and that is probably when those
things got re-enabled. I'll keep an eye out for any future
announcements from them.
Chuck
On Wed, Sep 12, 2012 at 1:05 AM, Vacheh David Sardarian