dubey/WebGoat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Introduction Sectin altered

Browse Source 
git-svn-id: http://webgoat.googlecode.com/svn/trunk@330 4033779f-a91e-0410-96ef-6bf7bf53c507
This commit is contained in:
wirth.marcel
2008-04-14 07:42:28 +00:00
parent bb327cc3c8
commit ff64cf84c0
8 changed files with 58 additions and 252 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
webgoat/main/project/WebContent/lesson_plans/TomcatSetup.html
View File

@ -1,5 +1,5 @@
<!-- Start Instructions -->
<h1>How To Setup Tomcat</h1><br><br>
<h1>How To Configure Tomcat</h1><br><br>
<h2>Introduction</h2>
<p>WebGoat comes with a sane default setup for Tomcat. This page will explain the setup
and which further possibilites you have to setup Tomcat. This is just
@ -8,7 +8,7 @@ refer to the Tomcat documentation. Please note that all solutions
are written for the standard setup on port 80. If you use another configuration you have
to ajust the solution to your configuration.</p>
<h2>The standard Setup</h2>
<h2>The Standard Configuration</h2>
<p>There are two standard Tomcat setups. In this setups WebGoat is only reachable from within
the localhost.
Both are identically with the only difference
@ -47,12 +47,13 @@ In this example to port 8442:
<pre>
&lt;!-- Define a SSL HTTP/1.1 Connector on port 8442 --&gt;
&lt;Connector address=&quot;127.0.0.1&quot; port=&quot;8442&quot;...
</pre>
</pre>
<br>
<h3>Make WebGoat Reachable From Another Client</h3>
<p><b>THIS MAKES IT POSSIBLE TO REALLY ATTACK YOUR SERVER! DO NOT DO THIS
<p>THIS MAKES IT POSSIBLE TO REALLY ATTACK YOUR SERVER! DO NOT DO THIS
UNTIL YOU KNOW WHAT YOU ARE DOING. THIS CONFIGURATION SHOULD BE ONLY USED IN
SAVE NETWORKS!</b></p>
SAVE NETWORKS!</p>
<p>By its default configuration WebGoat is only
reachable within the localhost. In a laboratory or a class
there is maybe the need of having a server and a few clients.