<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Josef+Meixner</id>
		<title>OWASP - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Josef+Meixner"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/Josef_Meixner"/>
		<updated>2026-05-31T13:02:24Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=WebGoat_Installation&amp;diff=10896</id>
		<title>WebGoat Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=WebGoat_Installation&amp;diff=10896"/>
				<updated>2006-10-21T11:45:30Z</updated>
		
		<summary type="html">&lt;p&gt;Josef Meixner: /* Installing to Linux */ Formatting of start and stop command was off&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[WebGoat User Guide Table of Contents]]&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
WebGoat is a platform independent environment.&lt;br /&gt;
It utilizes Apache Tomcat and the JAVA development environment.&lt;br /&gt;
Installers are provided for Microsoft Windows and UN*X environments, together with notes for installation on other platforms.&lt;br /&gt;
&lt;br /&gt;
==Installing Java and Tomcat ==&lt;br /&gt;
# &amp;lt;This section may not be needed, update for v4&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==Installing to Windows ==&lt;br /&gt;
# Unzip the Windows_WebGoat-x.x.zip to your working environment &lt;br /&gt;
# To start Tomcat, browse to the WebGoat directory unzipped above and double click &amp;quot;webgoat.bat&amp;quot;&lt;br /&gt;
# Start your browser and browse to: &amp;lt;u&amp;gt;http://localhost/WebGoat/attack&amp;lt;/u&amp;gt; This link is case-sensitive. Make sure to use a large ‘W’ and ‘G’.&lt;br /&gt;
&lt;br /&gt;
==Installing to Linux ==&lt;br /&gt;
* 1. Download and install Java JDK 1.5 from Sun (http://java.sun.com)&lt;br /&gt;
* 2. Unzip the Unix_WebGoat-x.x.zip to your working directory&lt;br /&gt;
* 3. Edit the following line in webgoat.sh, set JAVA_HOME to your JDK1.5 path. &lt;br /&gt;
  JAVA_HOME=&amp;quot;SET ME TO YOUR JAVA 1.5 JDK PATH&amp;quot;&lt;br /&gt;
* 4. Since the latest version runs on a privileged port, you will need to start/stop WebGoat as root.&lt;br /&gt;
&lt;br /&gt;
 sudo sh webgoat.sh start&lt;br /&gt;
 sudo sh webgoat.sh stop&lt;br /&gt;
&lt;br /&gt;
==Installing to OS X (Tiger 10.4+) ==&lt;br /&gt;
# Unzip the Unix_WebGoat-x.x.zip to your working directory&lt;br /&gt;
# Since the latest version runs on a privileged port, you will need to start/stop WebGoat as root.&lt;br /&gt;
&lt;br /&gt;
	sudo sh webgoat.sh start&lt;br /&gt;
	sudo sh webgoat.sh stop&lt;br /&gt;
&lt;br /&gt;
==Running ==&lt;br /&gt;
# Start your browser and browse to: &amp;lt;u&amp;gt;http://localhost/WebGoat/attack&amp;lt;/u&amp;gt;. Notice the capital 'W' and 'G'&lt;br /&gt;
# Login in as: user = guest, password = guest&lt;br /&gt;
&lt;br /&gt;
==Building ==&lt;br /&gt;
Skip these steps if you just want to run WebGoat&lt;br /&gt;
&amp;lt;this section is incomplete&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[WebGoat User Guide Table of Contents]]&lt;br /&gt;
[[Category:OWASP WebGoat Project]]&lt;br /&gt;
{{Template:Stub}}&lt;/div&gt;</summary>
		<author><name>Josef Meixner</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Tools_required&amp;diff=10895</id>
		<title>Tools required</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Tools_required&amp;diff=10895"/>
				<updated>2006-10-21T11:19:49Z</updated>
		
		<summary type="html">&lt;p&gt;Josef Meixner: Missed second link at last edit&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[WebGoat User Guide Table of Contents]]&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
There are a number of tools to aid the wily application security assessor. By far the most relevant to this type of security assessment are local proxies and web/application spiders. To complete the full set of WebGoat lessons a web-proxy will be required. &lt;br /&gt;
&lt;br /&gt;
==Application Assessment Proxy ==&lt;br /&gt;
A normal web-proxy typically receives, processes and forwards HTTP and HTTPS traffic between the client and server. This is normally to provide a single point through which all web traffic passes – for example to monitor usage, improve performance through caching or apply security policies.&lt;br /&gt;
&lt;br /&gt;
An application proxy tool is designed to intercept all HTTP and HTTPS communication between the local client browser and the server-side. It acts as a man-in-the-middle where all interaction may be monitored, reviewed and (importantly) modified.&lt;br /&gt;
&lt;br /&gt;
Through such a tool, the assessor can determine exactly what data is passed between the Client and Server. Furthermore, they may analyze and modify the data in order to test the impact of the application.&lt;br /&gt;
&lt;br /&gt;
It is essential for many of the lessons within WebGoat that an application assessment proxy, or software with equivalent functionality be used.&lt;br /&gt;
&lt;br /&gt;
The following is recommended:&lt;br /&gt;
WebScarab: &amp;lt;u&amp;gt;[[:Category:OWASP_WebScarab_Project|WebScarab Project]]&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Application Spider ==&lt;br /&gt;
Spidering or crawling a site should identify and follow all of the intended pages and links within a web site &amp;amp; application, and optionally store a local copy.&lt;br /&gt;
&lt;br /&gt;
The results can then be analyzed to define a comprehensive list of target scripts, forms, pages and fields within the application for use in later testing.&lt;br /&gt;
&lt;br /&gt;
Mirrored content can also be analyzed for relevant information far more quickly than through a manual or ‘on the wire’ analysis.&lt;br /&gt;
&lt;br /&gt;
The following are recommended:&lt;br /&gt;
* HHTrack – &amp;lt;u&amp;gt;http://www.httrack.com&amp;lt;/u&amp;gt;&lt;br /&gt;
* Form Scalpel – &amp;lt;u&amp;gt;http://www.ugc-labs.co.uk/tools/formscalpel/&amp;lt;/u&amp;gt;&lt;br /&gt;
* WebScarab – &amp;lt;u&amp;gt;[[:Category:OWASP_WebScarab_Project|WebScarab Project]]&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[WebGoat User Guide Table of Contents]]&lt;br /&gt;
[[Category:OWASP WebGoat Project]]&lt;/div&gt;</summary>
		<author><name>Josef Meixner</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Tools_required&amp;diff=10894</id>
		<title>Tools required</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Tools_required&amp;diff=10894"/>
				<updated>2006-10-21T11:19:03Z</updated>
		
		<summary type="html">&lt;p&gt;Josef Meixner: http://www.owasp.org/webscarab does no longer work, so substituted with category page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[WebGoat User Guide Table of Contents]]&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
There are a number of tools to aid the wily application security assessor. By far the most relevant to this type of security assessment are local proxies and web/application spiders. To complete the full set of WebGoat lessons a web-proxy will be required. &lt;br /&gt;
&lt;br /&gt;
==Application Assessment Proxy ==&lt;br /&gt;
A normal web-proxy typically receives, processes and forwards HTTP and HTTPS traffic between the client and server. This is normally to provide a single point through which all web traffic passes – for example to monitor usage, improve performance through caching or apply security policies.&lt;br /&gt;
&lt;br /&gt;
An application proxy tool is designed to intercept all HTTP and HTTPS communication between the local client browser and the server-side. It acts as a man-in-the-middle where all interaction may be monitored, reviewed and (importantly) modified.&lt;br /&gt;
&lt;br /&gt;
Through such a tool, the assessor can determine exactly what data is passed between the Client and Server. Furthermore, they may analyze and modify the data in order to test the impact of the application.&lt;br /&gt;
&lt;br /&gt;
It is essential for many of the lessons within WebGoat that an application assessment proxy, or software with equivalent functionality be used.&lt;br /&gt;
&lt;br /&gt;
The following is recommended:&lt;br /&gt;
WebScarab: &amp;lt;u&amp;gt;[[:Category:OWASP_WebScarab_Project|WebScarab Project]]&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Application Spider ==&lt;br /&gt;
Spidering or crawling a site should identify and follow all of the intended pages and links within a web site &amp;amp; application, and optionally store a local copy.&lt;br /&gt;
&lt;br /&gt;
The results can then be analyzed to define a comprehensive list of target scripts, forms, pages and fields within the application for use in later testing.&lt;br /&gt;
&lt;br /&gt;
Mirrored content can also be analyzed for relevant information far more quickly than through a manual or ‘on the wire’ analysis.&lt;br /&gt;
&lt;br /&gt;
The following are recommended:&lt;br /&gt;
* HHTrack – &amp;lt;u&amp;gt;http://www.httrack.com&amp;lt;/u&amp;gt;&lt;br /&gt;
* Form Scalpel – &amp;lt;u&amp;gt;http://www.ugc-labs.co.uk/tools/formscalpel/&amp;lt;/u&amp;gt;&lt;br /&gt;
* WebScarab – &amp;lt;u&amp;gt;http://www.owasp.org/webscarab&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[WebGoat User Guide Table of Contents]]&lt;br /&gt;
[[Category:OWASP WebGoat Project]]&lt;/div&gt;</summary>
		<author><name>Josef Meixner</name></author>	</entry>

	</feed>