<?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=Greggles</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=Greggles"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/Greggles"/>
		<updated>2026-04-16T01:52:40Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=PHP_CSRF_Guard&amp;diff=122990</id>
		<title>PHP CSRF Guard</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=PHP_CSRF_Guard&amp;diff=122990"/>
				<updated>2012-01-20T22:45:35Z</updated>
		
		<summary type="html">&lt;p&gt;Greggles: link to download&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==PHP CSRF Guard==&lt;br /&gt;
&lt;br /&gt;
If you need to protect against CSRF attacks in your code, this little helper can reduce the risk. &lt;br /&gt;
&lt;br /&gt;
===Architectural Issues===&lt;br /&gt;
&lt;br /&gt;
The main issue with CSRF is the lack of &amp;quot;authentication&amp;quot; of a privileged function. Therefore, in combination with this helper, you should:&lt;br /&gt;
&lt;br /&gt;
* Low value: Consider asking the user (on a new page / form) to re-authenticate using their password to confirm the action &lt;br /&gt;
* Medium value: Consider the use of second-factor authentication, such as sending the user an e-mail or SMS message with a random token which they must enter&lt;br /&gt;
* High value: disconnected calculator transaction signing the transaction&lt;br /&gt;
&lt;br /&gt;
===Using this code===&lt;br /&gt;
&lt;br /&gt;
* Download the code (see [https://www.owasp.org/index.php/Category:OWASP_CSRFGuard_Project OWASP CSRFGuard Project page] for github details)&lt;br /&gt;
* Include it within your project&lt;br /&gt;
* Use the object to create a hidden field Inside your forms, like this:&lt;br /&gt;
&lt;br /&gt;
 ?&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;form ... &amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;input ...&amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;?php echo $cg; ?&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;/form&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;/code&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you take the form submission, assert the form's validity:&lt;br /&gt;
&lt;br /&gt;
 try&lt;br /&gt;
 {&lt;br /&gt;
     $cg-&amp;gt;isValid();&lt;br /&gt;
     // your code here&lt;br /&gt;
 }&lt;br /&gt;
 catch (TokenException $e)&lt;br /&gt;
 {&lt;br /&gt;
   // handle exception &lt;br /&gt;
 }&lt;br /&gt;
 catch (// your exceptions here)&lt;br /&gt;
&lt;br /&gt;
===Caveats on use===&lt;br /&gt;
&lt;br /&gt;
This code is object-orientated. It relies upon PHP 5 only features, and throws a custom exception type. You should familiarize yourself with this coding style if you are still practicing function based PHP coding. It's not hard - see above. &lt;br /&gt;
&lt;br /&gt;
The code is PHP 5 only as this is the safest and most secure version of PHP available today. Your apps should be using PHP 5.2 or later to ensure that your application is running on a secure foundation. &lt;br /&gt;
&lt;br /&gt;
===LIcense===&lt;br /&gt;
&lt;br /&gt;
To allow widespread adoption, this code is licensed under the Creative Commons Share Alike 2.5 License. This allows you to use this in commercial and non-commercial applications alike. This license is GPL friendly.&lt;/div&gt;</summary>
		<author><name>Greggles</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Denver&amp;diff=34415</id>
		<title>Denver</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Denver&amp;diff=34415"/>
				<updated>2008-07-21T20:11:33Z</updated>
		
		<summary type="html">&lt;p&gt;Greggles: adding helpful link to Grendel-Scan home page.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Denver|extra=Chapter leaders are [mailto:eduprey@gmail.com Eric Duprey] and [mailto:owasp@electricalchemy.org David Campbell].   |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-denver|emailarchives=http://lists.owasp.org/pipermail/owasp-denver}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Next Meeting ==&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting: 16 July 2008 ===&lt;br /&gt;
&lt;br /&gt;
The next meeting is&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, '''July 16th''', 2008 at [http://rpsc.raytheon.com/ Raytheon Polar Services] === &lt;br /&gt;
at [http://maps.google.com/maps?f=q&amp;amp;hl=en&amp;amp;q=7400+s.+tucson+way+80112&amp;amp;ie=UTF8&amp;amp;ll=39.584425,-104.837079&amp;amp;spn=0.007227,0.013089&amp;amp;z=16&amp;amp;iwloc=addr 7400 S. Tucson Way, Centennial, CO 80112].  &lt;br /&gt;
&lt;br /&gt;
===Intro to Grendel - a WebApp PenTesting Tool - BRING A LAPTOP===&lt;br /&gt;
David Byrne and Eric Duprey will be presenting their latest work - [http://www.grendel-scan.com/ Grendel-Scan].  Grendel is a tool that's been developed to automate some appsec testing.  &lt;br /&gt;
&lt;br /&gt;
During this presentation, these guys will show how to use Grendel to accelerate webapp pen testing. &lt;br /&gt;
&lt;br /&gt;
David Byrne is an infosec veteran, with experience ranging from penetration testing for Fortune 100's to architecting security solutions for large multinational financials to consulting for government agencies. David is presently part of the team at Trustwave. &lt;br /&gt;
&lt;br /&gt;
Eric Duprey is a Senior Security Engineer for Dish Network Corporation and co-leader of the Denver OWASP Chapter. &lt;br /&gt;
&lt;br /&gt;
Updates will be spammed to the Chapter Mailing List.&lt;br /&gt;
&lt;br /&gt;
Agenda:&lt;br /&gt;
&lt;br /&gt;
6-6:30  Dinner (at Raytheon Polar; pizza provided by [http://www.trustwave.com TrustWave].&lt;br /&gt;
&lt;br /&gt;
6:30 - 6:40  Chapter business&lt;br /&gt;
&lt;br /&gt;
6:40 - 8:00  Presentation and Q&amp;amp;A&lt;br /&gt;
&lt;br /&gt;
Following the meeting we will have informal discussions over beverages at [http://maps.google.com/maps?f=q&amp;amp;hl=en&amp;amp;q=jd+bait+shop+denver&amp;amp;ie=UTF8&amp;amp;z=10&amp;amp;iwloc=A JD's Bait Shop].&lt;br /&gt;
&lt;br /&gt;
-----------------------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Questions, Comments===&lt;br /&gt;
Questions can be directed to &lt;br /&gt;
*[mailto:dcampbell@owasp.org David Campbell, Denver OWASP]&lt;br /&gt;
*[mailto:eduprey@gmail.com Eric Duprey, Denver OWASP]&lt;br /&gt;
&lt;br /&gt;
== Future Meetings == &lt;br /&gt;
&lt;br /&gt;
16 July 2008: David Byrne and Eric Duprey: Presenting a brand new Open Source Web-App Vulnerability Scanner!&lt;br /&gt;
&lt;br /&gt;
[http://www.denimgroup.com/about_team_dan.html 20 August 2008: Dan Cornell]&lt;br /&gt;
&lt;br /&gt;
September 2008: available&lt;br /&gt;
&lt;br /&gt;
October 2008: available&lt;br /&gt;
&lt;br /&gt;
November 2008: available&lt;br /&gt;
&lt;br /&gt;
December 2008: available&lt;br /&gt;
&lt;br /&gt;
== Past Meetings ==&lt;br /&gt;
&lt;br /&gt;
[[Front Range OWASP Conference|June 2008]]&lt;br /&gt;
&lt;br /&gt;
[[Denver May 2008 meeting|May 2008]]&lt;br /&gt;
&lt;br /&gt;
[[Denver April 2008 meeting|April 2008]]&lt;br /&gt;
&lt;br /&gt;
[[Denver February 2008 meeting|February 2008]]&lt;br /&gt;
&lt;br /&gt;
[[Denver June 2007 meeting|June 2007]]&lt;br /&gt;
&lt;br /&gt;
[[Denver April 2007 meeting|April 2007]]&lt;br /&gt;
&lt;br /&gt;
[[Denver February 2007 meeting|February 2007]]&lt;br /&gt;
&lt;br /&gt;
[[Denver January 2007 meeting|January 2007]]&lt;br /&gt;
&lt;br /&gt;
[[Denver November 2006 meeting|November 2006]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==Chapter Planning Pages==&lt;br /&gt;
[[Front Range Web Application Security Summit Planning Page|Front Range Web Application Security Summit Planning]]&lt;/div&gt;</summary>
		<author><name>Greggles</name></author>	</entry>

	</feed>