https://wiki.owasp.org/api.php?action=feedcontributions&feedformat=atom&user=Jason+JohnsonOWASP - User contributions [en]2026-05-09T07:10:39ZUser contributionsMediaWiki 1.27.2https://wiki.owasp.org/index.php?title=Oklahoma_City&diff=173047Oklahoma City2014-04-19T16:58:05Z<p>Jason Johnson: </p>
<hr />
<div>[[File:banner.png]]<br />
[[File:facebook.png|link=https://www.facebook.com/pages/OWASP-OKC/423488184386817?fref=ts]][[File:twitter.png|link=https://twitter.com/OWASPOKC]]<br />
<br />
[[Image:Btn_donate_SM.gif|link=http://www.regonline.com/donation_1044369]] to a chapter or become a local chapter supporter.<br />
<br />
Or consider the value of [http://www.owasp.org/index.php/Membership Individual, Corporate, or Academic Supporter membership]. Ready to become a member? [[Image:Join_Now_BlueIcon.JPG|75px|link=https://www.owasp.org/index.php/Membership_Map]]<br />
<br />
The chapter leaders are [mailto:jason.johnson@owasp.org Jason Johnson]<br />
<br />
[[Image:mail.png|120px|link=https://lists.owasp.org/mailman/listinfo/owasp-oklahoma_city]]<br />
[[Image:archivemail.png|120px|link=http://lists.owasp.org/pipermail/owasp-oklahoma_city/]]<br />
<br />
<br />
== Local News ==<br />
<br />
[[Category:OWASP Chapter]]<br />
[[Category:United States]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=168083OWASP Hive Project2014-02-13T16:39:22Z<p>Jason Johnson: </p>
<hr />
<div>=Main=<br />
<br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
==OWASP HIVE==<br />
<br />
OWASP HIVE project is an idea for a learning platform by using some small capable pc to do our bidding.<br />
<br />
==Introduction==<br />
<br />
The issue - to be a hive we need to connect in some kind of secure anonymous cool way! Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. <br />
<br />
==Description==<br />
<br />
This learning environment can be used for teaching and proof of concept for projects.<br />
<br />
<br />
==Licensing==<br />
OWASP HIVE is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.<br />
<br />
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
== What is HIVE? ==<br />
<br />
OWASP HIVE provides:<br />
<br />
* Teaching Environment<br />
* Secure storage grid<br />
* Testing grounds for secure code vs non-secure code.<br />
* Anything you want to create<br />
<br />
<br />
== Presentation ==<br />
<br />
http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy<br />
<br />
<br />
<br />
<br />
== Project Leader ==<br />
<br />
[mailto:jason.johnson@owasp.org Jason Johnson]<br />
<br />
<br />
== Related Projects ==<br />
<br />
* [[OWASP_CISO_Survey]]<br />
<br />
<br />
<br />
| valign="top" style="padding-left:25px;width:200px;" | <br />
<br />
== Quick Download ==<br />
<br />
* Link to page/download<br />
<br />
<br />
<br />
== News and Events ==<br />
* [13 FEB 2014] OSU is doing a semester of R&D on the HIVE. What will they make???<br />
<br />
<br />
== In Print ==<br />
<br />
==Classifications==<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]] <br />
|-<br />
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
; Q1<br />
: A1<br />
<br />
; Q2<br />
: A2<br />
<br />
= Acknowledgements =<br />
==Volunteers==<br />
HIVE is developed by a worldwide team of volunteers. The primary contributors to date have been:<br />
<br />
* OSU <br />
* Oklahoma City (The 404) <br />
<br />
==Others==<br />
* xxx<br />
* xxx<br />
<br />
= Road Map and Getting Involved =<br />
As of FEB 13, the priorities are:<br />
* Create a control interface<br />
<br />
Involvement in the development and promotion of The HIVE is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Document your ideas<br />
* Make us logos<br />
* Help us develop course work<br />
* Get us in touch with educators so we can help spread the word<br />
<br />
<br />
<br />
=Project About=<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
__NOTOC__ <headertabs /> <br />
<br />
[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=168082OWASP Hive Project2014-02-13T16:37:30Z<p>Jason Johnson: </p>
<hr />
<div>=Main=<br />
<br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
==OWASP HIVE==<br />
<br />
OWASP HIVE project is an idea for a learning platform by using some small capable pc to do our bidding.<br />
<br />
==Introduction==<br />
<br />
The issue - to be a hive we need to connect in some kind of secure anonymous cool way! Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. <br />
<br />
==Description==<br />
<br />
This learning environment can be used for teaching and proof of concept for projects.<br />
<br />
<br />
==Licensing==<br />
OWASP HIVE is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.<br />
<br />
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
== What is HIVE? ==<br />
<br />
OWASP HIVE provides:<br />
<br />
* Teaching Environment<br />
* Secure storage grid<br />
* Testing grounds for secure code vs non-secure code.<br />
* Anything you want to create<br />
<br />
<br />
== Presentation ==<br />
<br />
http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy<br />
<br />
<br />
<br />
<br />
== Project Leader ==<br />
<br />
Jason Johnson<br />
<br />
<br />
== Related Projects ==<br />
<br />
* [[OWASP_CISO_Survey]]<br />
<br />
<br />
<br />
| valign="top" style="padding-left:25px;width:200px;" | <br />
<br />
== Quick Download ==<br />
<br />
* Link to page/download<br />
<br />
<br />
<br />
== News and Events ==<br />
* [13 FEB 2014] OSU is doing a semester of R&D on the HIVE. What will they make???<br />
<br />
<br />
== In Print ==<br />
<br />
==Classifications==<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]] <br />
|-<br />
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
; Q1<br />
: A1<br />
<br />
; Q2<br />
: A2<br />
<br />
= Acknowledgements =<br />
==Volunteers==<br />
HIVE is developed by a worldwide team of volunteers. The primary contributors to date have been:<br />
<br />
* OSU <br />
* Oklahoma City (The 404) <br />
<br />
==Others==<br />
* xxx<br />
* xxx<br />
<br />
= Road Map and Getting Involved =<br />
As of FEB 13, the priorities are:<br />
* Create a control interface<br />
<br />
Involvement in the development and promotion of The HIVE is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Document your ideas<br />
* Make us logos<br />
* Help us develop course work<br />
* Get us in touch with educators so we can help spread the word<br />
<br />
<br />
<br />
=Project About=<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
__NOTOC__ <headertabs /> <br />
<br />
[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=168079OWASP Hive Project2014-02-13T16:02:55Z<p>Jason Johnson: </p>
<hr />
<div>=Main=<br />
<br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
==OWASP HIVE==<br />
<br />
OWASP HIVE project is an idea for a learning platform by using some small capable pc to do our bidding.<br />
<br />
==Introduction==<br />
<br />
The issue - to be a hive we need to connect in some kind of secure anonymous cool way! Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. <br />
<br />
==Description==<br />
<br />
This learning environment can be used for teaching and proof of concept for projects.<br />
<br />
<br />
==Licensing==<br />
OWASP HIVE is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.<br />
<br />
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
== What is HIVE? ==<br />
<br />
OWASP HIVE provides:<br />
<br />
* Teaching Environment<br />
* Secure storage grid<br />
* Testing grounds for secure code vs non-secure code.<br />
* Anything you want to create<br />
<br />
<br />
== Presentation ==<br />
<br />
http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy<br />
<br />
<br />
<br />
<br />
== Project Leader ==<br />
<br />
Jason Johnson<br />
<br />
<br />
== Related Projects ==<br />
<br />
* [[OWASP_CISO_Survey]]<br />
<br />
<br />
<br />
| valign="top" style="padding-left:25px;width:200px;" | <br />
<br />
== Quick Download ==<br />
<br />
* Link to page/download<br />
<br />
<br />
<br />
== News and Events ==<br />
* [13 FEB 2014] OSU is doing a semester of R&D on the HIVE. What will they make???<br />
<br />
<br />
== In Print ==<br />
<br />
==Classifications==<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]] <br />
|-<br />
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
; Q1<br />
: A1<br />
<br />
; Q2<br />
: A2<br />
<br />
= Acknowledgements =<br />
==Volunteers==<br />
HIVE is developed by a worldwide team of volunteers. The primary contributors to date have been:<br />
<br />
* OSU <br />
* Oklahoma City (The 404) <br />
<br />
==Others==<br />
* xxx<br />
* xxx<br />
<br />
= Road Map and Getting Involved =<br />
As of FEB 13, the priorities are:<br />
* Create a control interface<br />
* xxx<br />
* xxx<br />
<br />
Involvement in the development and promotion of XXX is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* xxx<br />
* xxx<br />
<br />
<br />
<br />
=Project About=<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
__NOTOC__ <headertabs /> <br />
<br />
[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=Projects/OWASP_Hive_Project&diff=159382Projects/OWASP Hive Project2013-09-27T20:00:23Z<p>Jason Johnson: </p>
<hr />
<div>{{Template:Project About<br />
| project_name = OWASP_Hive <br />
| project_home_page = http://netgreen.us<br />
| project_description = The HIVE is a bunch of small computers in a cluster or stand alone. <br />
'''hive''' (noun)<br />
;1. THE HIVE <br />
:a. Structure for housing bees aka (WASPS), especially owasps.<br />
:b. Colony of bees/owasps living in such a structure.<br />
:2. A place swarming with activity.<br />
:v. hived, hiv·ing, hives <br />
:'''1. To collect into a hive.'''<br />
:'''2. To store (data) in a hive.'''<br />
:'''3. To store up; accumulate.'''<br />
:v.intr.<br />
:1. To enter and occupy a hive or network.<br />
:2. To live with many others in close association (OWASP).<br />
;Phrasal Verb: <br />
:'''hive off (term used when gathering)'''<br />
:To set apart from a group: hived off the department into another division.<br />
| leader_name1 =Jason Johnson<br />
| leader_email1 =Jason.Johnson@owasp.org <br />
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp_hive_project<br />
| project_road_map = https://www.owasp.org/index.php/Projects/OWASP_Hive_Project/Roadmap<br />
| presentation_link = http://prezi.com/ffc3mt-f8jd6/untitled-prezi/?utm_campaign=share&utm_medium=copy<br />
}}</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=Projects/OWASP_Hive_Project&diff=159381Projects/OWASP Hive Project2013-09-27T20:00:01Z<p>Jason Johnson: </p>
<hr />
<div>{{Template:Project About<br />
| project_name = OWASP_Hive <br />
| project_home_page = [http://netgreen.us/ Home Page]<br />
| project_description = The HIVE is a bunch of small computers in a cluster or stand alone. <br />
'''hive''' (noun)<br />
;1. THE HIVE <br />
:a. Structure for housing bees aka (WASPS), especially owasps.<br />
:b. Colony of bees/owasps living in such a structure.<br />
:2. A place swarming with activity.<br />
:v. hived, hiv·ing, hives <br />
:'''1. To collect into a hive.'''<br />
:'''2. To store (data) in a hive.'''<br />
:'''3. To store up; accumulate.'''<br />
:v.intr.<br />
:1. To enter and occupy a hive or network.<br />
:2. To live with many others in close association (OWASP).<br />
;Phrasal Verb: <br />
:'''hive off (term used when gathering)'''<br />
:To set apart from a group: hived off the department into another division.<br />
| leader_name1 =Jason Johnson<br />
| leader_email1 =Jason.Johnson@owasp.org <br />
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp_hive_project<br />
| project_road_map = https://www.owasp.org/index.php/Projects/OWASP_Hive_Project/Roadmap<br />
| presentation_link = http://prezi.com/ffc3mt-f8jd6/untitled-prezi/?utm_campaign=share&utm_medium=copy<br />
}}</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=Projects/OWASP_Hive_Project&diff=159380Projects/OWASP Hive Project2013-09-27T19:59:23Z<p>Jason Johnson: </p>
<hr />
<div>{{Template:Project About<br />
| project_name = OWASP_Hive [http://netgreen.us/ Home Page]<br />
| project_home_page = http://netgreen.us<br />
| project_description = The HIVE is a bunch of small computers in a cluster or stand alone. <br />
'''hive''' (noun)<br />
;1. THE HIVE <br />
:a. Structure for housing bees aka (WASPS), especially owasps.<br />
:b. Colony of bees/owasps living in such a structure.<br />
:2. A place swarming with activity.<br />
:v. hived, hiv·ing, hives <br />
:'''1. To collect into a hive.'''<br />
:'''2. To store (data) in a hive.'''<br />
:'''3. To store up; accumulate.'''<br />
:v.intr.<br />
:1. To enter and occupy a hive or network.<br />
:2. To live with many others in close association (OWASP).<br />
;Phrasal Verb: <br />
:'''hive off (term used when gathering)'''<br />
:To set apart from a group: hived off the department into another division.<br />
| leader_name1 =Jason Johnson<br />
| leader_email1 =Jason.Johnson@owasp.org <br />
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp_hive_project<br />
| project_road_map = https://www.owasp.org/index.php/Projects/OWASP_Hive_Project/Roadmap<br />
| presentation_link = http://prezi.com/ffc3mt-f8jd6/untitled-prezi/?utm_campaign=share&utm_medium=copy<br />
}}</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=Projects/OWASP_Hive_Project&diff=159379Projects/OWASP Hive Project2013-09-27T19:58:37Z<p>Jason Johnson: </p>
<hr />
<div>{{Template:Project About<br />
| project_name = OWASP_Hive<br />
| project_home_page = http://netgreen.us<br />
| project_description = The HIVE is a bunch of small computers in a cluster or stand alone. <br />
'''hive''' (noun)<br />
;1. THE HIVE <br />
:a. Structure for housing bees aka (WASPS), especially owasps.<br />
:b. Colony of bees/owasps living in such a structure.<br />
:2. A place swarming with activity.<br />
:v. hived, hiv·ing, hives <br />
:'''1. To collect into a hive.'''<br />
:'''2. To store (data) in a hive.'''<br />
:'''3. To store up; accumulate.'''<br />
:v.intr.<br />
:1. To enter and occupy a hive or network.<br />
:2. To live with many others in close association (OWASP).<br />
;Phrasal Verb: <br />
:'''hive off (term used when gathering)'''<br />
:To set apart from a group: hived off the department into another division.<br />
| leader_name1 =Jason Johnson<br />
| leader_email1 =Jason.Johnson@owasp.org <br />
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp_hive_project<br />
| project_road_map = https://www.owasp.org/index.php/Projects/OWASP_Hive_Project/Roadmap<br />
| presentation_link = http://prezi.com/ffc3mt-f8jd6/untitled-prezi/?utm_campaign=share&utm_medium=copy<br />
}}</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=Projects/OWASP_Hive_Project&diff=159378Projects/OWASP Hive Project2013-09-27T19:57:57Z<p>Jason Johnson: </p>
<hr />
<div>{{Template:Project About<br />
| project_name = OWASP_Hive<br />
| project_home_page = [http://netgreen.us/ HIVE homepage]<br />
| project_description = The HIVE is a bunch of small computers in a cluster or stand alone. <br />
'''hive''' (noun)<br />
;1. THE HIVE <br />
:a. Structure for housing bees aka (WASPS), especially owasps.<br />
:b. Colony of bees/owasps living in such a structure.<br />
:2. A place swarming with activity.<br />
:v. hived, hiv·ing, hives <br />
:'''1. To collect into a hive.'''<br />
:'''2. To store (data) in a hive.'''<br />
:'''3. To store up; accumulate.'''<br />
:v.intr.<br />
:1. To enter and occupy a hive or network.<br />
:2. To live with many others in close association (OWASP).<br />
;Phrasal Verb: <br />
:'''hive off (term used when gathering)'''<br />
:To set apart from a group: hived off the department into another division.<br />
| leader_name1 =Jason Johnson<br />
| leader_email1 =Jason.Johnson@owasp.org <br />
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp_hive_project<br />
| project_road_map = https://www.owasp.org/index.php/Projects/OWASP_Hive_Project/Roadmap<br />
| presentation_link = http://prezi.com/ffc3mt-f8jd6/untitled-prezi/?utm_campaign=share&utm_medium=copy<br />
}}</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=159370OWASP Hive Project2013-09-27T19:30:37Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<br />
gggrgM**M#mggg__<br />
__wgNN@"B*P""mp""@d#"@N#Nw__<br />
_g#@0F_a*F# _*F9m_ ,F9*__9NG#g_<br />
_mN#F aM" #p" !q@ 9NL "9#Qu_<br />
g#MF _pP"L _g@"9L_ _g""#__ g"9w_ 0N#p<br />
_0F jL*" 7_wF #_gF 9gjF "bJ 9h_<br />
j# gAF _@NL WELCOME J@u_ 2#_ #_<br />
,FF_#" 9_ _#" "b_ g@ "hg _#" !q_ jF "*_09_<br />
F N" #p" Ng@ TO `#g" "w@ "# t<br />
j p# g"9_ g@"9_ gP"#_ gF"q Pb L<br />
0J k _@ 9g_ j#" "b_ j#" "b_ _d" q_ g ##<br />
#F `NF "#g" THE "Md" GRID 5N# 9W" j#<br />
#k jFb_ g@"q_ _*"9m_ _*"R_ _#Np J#<br />
tApjF 9g J" 9M_ _m" 9%_ _*" "# gF 9_jNF<br />
k`N "q# 9g@ #gF ##" #"j<br />
`_0q_ #"q_ _&"9p_ _g"`L_ _*"# jAF,'<br />
9# "b_j "b_ g" *g _gF 9_ g#" "L_*"qNF<br />
"b_ "#_ "NL _B# _I@ j#" _#"<br />
NM_0"*g_ j""9u_ gP q_ _w@ ]_ _g*"F_g@<br />
"NNh_ !w#_ 9#g" "m*" _#*" _dN@"<br />
9##g_0@q__ #"4_ j*"k __*NF_g#@P"<br />
"9NN#gIPNL_ "b@" _2M"Lg#N@F"<br />
""P@*NN#gEZgNN@#@P""<br />
<br />
=Temp introducer URL= <br />
''' email me and I will give you the details if you would like to try the test grid '''<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform by using some small capable pc to do our bidding. That works very well you can stand up a gazillion different servers if you want. The issue - to be a hive we need to connect in some kind of secure anonymous cool way! Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like<br />
<br />
URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3<br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
One way I can see the HIVE used is a file archive10-1000 nodes strong. Or even a perk or prize like anonymous storage for OWASP members. The end goal is to provide a global grid for all with any amount of users that can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
''The milestones that I anticipate are:''<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
<br />
<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158930OWASP GSD Project2013-09-23T20:04:53Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply (approx 80$ before wiring and mounted)<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''More infomation can be found on the[https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
Milestones that I anticipate are.<br />
*Sweet user interface.<br />
*Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
*Make a proposal to OWASP for a more stable introducer and private GRID. <br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158929OWASP GSD Project2013-09-23T20:03:34Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''More infomation can be found on the[https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
***The milestones that I anticipate are.<br />
*Sweet user interface.<br />
*Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
*Make a proposal to OWASP for a more stable introducer and private GRID. <br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158928OWASP GSD Project2013-09-23T20:02:13Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! More infomation can be found on the[https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
***The milestones that I anticipate are.<br />
*Sweet user interface.<br />
*Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
*Make a proposal to OWASP for a more stable introducer and private GRID. <br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158927OWASP GSD Project2013-09-23T20:01:44Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! More infomation can be found on the[https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
*** The milestones that I anticipate are.<br />
* Sweet user interface.<br />
* Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
* Make a proposal to OWASP for a more stable introducer and private GRID. <br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158926OWASP GSD Project2013-09-23T20:00:57Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! More infomation can be found on the[https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
*** The milestones that I anticipate are:<br />
* Sweet user interface<br />
* Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
* Make a proposal to OWASP for a more stable introducer and private GRID. <br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158925OWASP GSD Project2013-09-23T20:00:24Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! More infomation can be found on the[https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
*** '''The milestones that I anticipate are:<br />
* Sweet user interface<br />
* Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
* Make a proposal to OWASP for a more stable introducer and private GRID. <br />
<br />
<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158924OWASP GSD Project2013-09-23T19:59:33Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret!<br />
<br />
More infomation can be found on the [https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
***The milestones that I anticipate are:<br />
**Sweet user interface<br />
**Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
**Make a proposal to OWASP for a more stable introducer and private GRID. <br />
<br />
<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158923OWASP GSD Project2013-09-23T19:58:36Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret!<br />
''' More infomation can be found on the [https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
''' The milestones that I anticipate are:<br />
** ''' Sweet user interface<br />
** ''' Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
** ''' Make a proposal to OWASP for a more stable introducer and private GRID. <br />
<br />
<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158922OWASP GSD Project2013-09-23T19:57:54Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret!<br />
** ''' More infomation can be found on the [https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
*The milestones that I anticipate are:<br />
** ''' Sweet user interface<br />
** ''' Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
** ''' Make a proposal to OWASP for a more stable introducer and private GRID. <br />
<br />
<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158921OWASP GSD Project2013-09-23T19:57:25Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret!<br />
** ''' More infomation can be found on the [https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
== The milestones that I anticipate are:<br />
** ''' Sweet user interface<br />
** ''' Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
** ''' Make a proposal to OWASP for a more stable introducer and private GRID. <br />
<br />
<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158920OWASP GSD Project2013-09-23T19:56:33Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret!<br />
** ''' More infomation can be found on the [https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
** ''' =The milestones that I anticipate are:=<br />
** ''' Sweet user interface<br />
** ''' Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. <br />
** ''' Make a proposal to OWASP for a more stable introducer and private GRID. <br />
<br />
<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158919OWASP GSD Project2013-09-23T19:55:43Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone HIVE Cluster''' - Cost for 10 Environment Hive 1600.00 (Approx)<br />
*** '''HIVE Power''' - 20Amp 5v power supply<br />
*** '''HIVE Switches''' - 1G 5Port Switch Cost 40.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)(still need case Ideas for this)<br />
*** '''WiFi Mod''' - Cost 6.00 (per BB)<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret!<br />
** ''' More infomation can be found on the [https://www.owasp.org/index.php/OWASP_Hive_Project Hive Project]<br />
** ''' The milestones that I anticipate are:<br />
**Sweet user interface<br />
**Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time.<br />
(Expand more on this) <br />
**Make a proposal to OWASP for a more stable introducer and private GRID. <br />
<br />
<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158917OWASP GSD Project2013-09-23T19:49:54Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone Cluster''' - Cost for 10 Environment Hive 600.00 (Approx) <br />
*** '''4gb miniSD Card''' - Cost 12.37 (per BB) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per BB)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret!<br />
** ''' More infomation can be found on the project page <br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158916OWASP Hive Project2013-09-23T19:49:28Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<br />
gggrgM**M#mggg__<br />
__wgNN@"B*P""mp""@d#"@N#Nw__<br />
_g#@0F_a*F# _*F9m_ ,F9*__9NG#g_<br />
_mN#F aM" #p" !q@ 9NL "9#Qu_<br />
g#MF _pP"L _g@"9L_ _g""#__ g"9w_ 0N#p<br />
_0F jL*" 7_wF #_gF 9gjF "bJ 9h_<br />
j# gAF _@NL WELCOME J@u_ 2#_ #_<br />
,FF_#" 9_ _#" "b_ g@ "hg _#" !q_ jF "*_09_<br />
F N" #p" Ng@ TO `#g" "w@ "# t<br />
j p# g"9_ g@"9_ gP"#_ gF"q Pb L<br />
0J k _@ 9g_ j#" "b_ j#" "b_ _d" q_ g ##<br />
#F `NF "#g" THE "Md" GRID 5N# 9W" j#<br />
#k jFb_ g@"q_ _*"9m_ _*"R_ _#Np J#<br />
tApjF 9g J" 9M_ _m" 9%_ _*" "# gF 9_jNF<br />
k`N "q# 9g@ #gF ##" #"j<br />
`_0q_ #"q_ _&"9p_ _g"`L_ _*"# jAF,'<br />
9# "b_j "b_ g" *g _gF 9_ g#" "L_*"qNF<br />
"b_ "#_ "NL _B# _I@ j#" _#"<br />
NM_0"*g_ j""9u_ gP q_ _w@ ]_ _g*"F_g@<br />
"NNh_ !w#_ 9#g" "m*" _#*" _dN@"<br />
9##g_0@q__ #"4_ j*"k __*NF_g#@P"<br />
"9NN#gIPNL_ "b@" _2M"Lg#N@F"<br />
""P@*NN#gEZgNN@#@P""<br />
<br />
=Temp introducer URL= <br />
''' email me and I will give you the details if you would like to try the test grid '''<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
''The milestones that I anticipate are:''<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
<br />
<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158915OWASP Hive Project2013-09-23T19:47:51Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<br />
gggrgM**M#mggg__<br />
__wgNN@"B*P""mp""@d#"@N#Nw__<br />
_g#@0F_a*F# _*F9m_ ,F9*__9NG#g_<br />
_mN#F aM" #p" !q@ 9NL "9#Qu_<br />
g#MF _pP"L _g@"9L_ _g""#__ g"9w_ 0N#p<br />
_0F jL*" 7_wF #_gF 9gjF "bJ 9h_<br />
j# gAF _@NL WELCOME J@u_ 2#_ #_<br />
,FF_#" 9_ _#" "b_ g@ "hg _#" !q_ jF "*_09_<br />
F N" #p" Ng@ TO `#g" "w@ "# t<br />
j p# g"9_ g@"9_ gP"#_ gF"q Pb L<br />
0J k _@ 9g_ j#" "b_ j#" "b_ _d" q_ g ##<br />
#F `NF "#g" THE "Md" GRID 5N# 9W" j#<br />
#k jFb_ g@"q_ _*"9m_ _*"R_ _#Np J#<br />
tApjF 9g J" 9M_ _m" 9%_ _*" "# gF 9_jNF<br />
k`N "q# 9g@ #gF ##" #"j<br />
`_0q_ #"q_ _&"9p_ _g"`L_ _*"# jAF,'<br />
9# "b_j "b_ g" *g _gF 9_ g#" "L_*"qNF<br />
"b_ "#_ "NL _B# _I@ j#" _#"<br />
NM_0"*g_ j""9u_ gP q_ _w@ ]_ _g*"F_g@<br />
"NNh_ !w#_ 9#g" "m*" _#*" _dN@"<br />
9##g_0@q__ #"4_ j*"k __*NF_g#@P"<br />
"9NN#gIPNL_ "b@" _2M"Lg#N@F"<br />
""P@*NN#gEZgNN@#@P""<br />
<br />
=Temp introducer URL= <br />
''' pb://o2fmouklqr72hnvdmk7rwu476bgbt2qf@tahoe.netgreen.us:35394,127.0.0.1:35394/introducer '''<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
''The milestones that I anticipate are:''<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
<br />
<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158914OWASP Hive Project2013-09-23T19:47:01Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<br />
gggrgM**M#mggg__<br />
__wgNN@"B*P""mp""@d#"@N#Nw__<br />
_g#@0F_a*F# _*F9m_ ,F9*__9NG#g_<br />
_mN#F aM" #p" !q@ 9NL "9#Qu_<br />
g#MF _pP"L _g@"9L_ _g""#__ g"9w_ 0N#p<br />
_0F jL*" 7_wF #_gF 9gjF "bJ 9h_<br />
j# gAF _@NL WELCOME J@u_ 2#_ #_<br />
,FF_#" 9_ _#" "b_ g@ "hg _#" !q_ jF "*_09_<br />
F N" #p" Ng@ TO `#g" "w@ "# t<br />
j p# g"9_ g@"9_ gP"#_ gF"q Pb L<br />
0J k _@ 9g_ j#" "b_ j#" "b_ _d" q_ g ##<br />
#F `NF "#g" THE "Md" GRID 5N# 9W" j#<br />
#k jFb_ g@"q_ _*"9m_ _*"R_ _#Np J#<br />
tApjF 9g J" 9M_ _m" 9%_ _*" "# gF 9_jNF<br />
k`N "q# 9g@ #gF ##" #"j<br />
`_0q_ #"q_ _&"9p_ _g"`L_ _*"# jAF,'<br />
9# "b_j "b_ g" *g _gF 9_ g#" "L_*"qNF<br />
"b_ "#_ "NL _B# _I@ j#" _#"<br />
NM_0"*g_ j""9u_ gP q_ _w@ ]_ _g*"F_g@<br />
"NNh_ !w#_ 9#g" "m*" _#*" _dN@"<br />
9##g_0@q__ #"4_ j*"k __*NF_g#@P"<br />
"9NN#gIPNL_ "b@" _2M"Lg#N@F"<br />
""P@*NN#gEZgNN@#@P""<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
''The milestones that I anticipate are:''<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
<br />
** Temp introducer URL <br />
''' pb://o2fmouklqr72hnvdmk7rwu476bgbt2qf@tahoe.netgreen.us:35394,127.0.0.1:35394/introducer '''<br />
<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158913OWASP Hive Project2013-09-23T19:45:30Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<br />
gggrgM**M#mggg__<br />
__wgNN@"B*P""mp""@d#"@N#Nw__<br />
_g#@0F_a*F# _*F9m_ ,F9*__9NG#g_<br />
_mN#F aM" #p" !q@ 9NL "9#Qu_<br />
g#MF _pP"L _g@"9L_ _g""#__ g"9w_ 0N#p<br />
_0F jL*" 7_wF #_gF 9gjF "bJ 9h_<br />
j# gAF _@NL WELCOME J@u_ 2#_ #_<br />
,FF_#" 9_ _#" "b_ g@ "hg _#" !q_ jF "*_09_<br />
F N" #p" Ng@ TO `#g" "w@ "# t<br />
j p# g"9_ g@"9_ gP"#_ gF"q Pb L<br />
0J k _@ 9g_ j#" "b_ j#" "b_ _d" q_ g ##<br />
#F `NF "#g" THE "Md" GRID 5N# 9W" j#<br />
#k jFb_ g@"q_ _*"9m_ _*"R_ _#Np J#<br />
tApjF 9g J" 9M_ _m" 9%_ _*" "# gF 9_jNF<br />
k`N "q# 9g@ #gF ##" #"j<br />
`_0q_ #"q_ _&"9p_ _g"`L_ _*"# jAF,'<br />
9# "b_j "b_ g" *g _gF 9_ g#" "L_*"qNF<br />
"b_ "#_ "NL _B# _I@ j#" _#"<br />
NM_0"*g_ j""9u_ gP q_ _w@ ]_ _g*"F_g@<br />
"NNh_ !w#_ 9#g" "m*" _#*" _dN@"<br />
9##g_0@q__ #"4_ j*"k __*NF_g#@P"<br />
"9NN#gIPNL_ "b@" _2M"Lg#N@F"<br />
""P@*NN#gEZgNN@#@P""<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
''The milestones that I anticipate are:''<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158912OWASP Hive Project2013-09-23T19:44:18Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<nowiki>__gggrgM**M#mggg__<br />
__wgNN@"B*P""mp""@d#"@N#Nw__<br />
_g#@0F_a*F# _*F9m_ ,F9*__9NG#g_<br />
_mN#F aM" #p" !q@ 9NL "9#Qu_<br />
g#MF _pP"L _g@"9L_ _g""#__ g"9w_ 0N#p<br />
_0F jL*" 7_wF #_gF 9gjF "bJ 9h_<br />
j# gAF _@NL WELCOME J@u_ 2#_ #_<br />
,FF_#" 9_ _#" "b_ g@ "hg _#" !q_ jF "*_09_<br />
F N" #p" Ng@ TO `#g" "w@ "# t<br />
j p# g"9_ g@"9_ gP"#_ gF"q Pb L<br />
0J k _@ 9g_ j#" "b_ j#" "b_ _d" q_ g ##<br />
#F `NF "#g" THE "Md" GRID 5N# 9W" j#<br />
#k jFb_ g@"q_ _*"9m_ _*"R_ _#Np J#<br />
tApjF 9g J" 9M_ _m" 9%_ _*" "# gF 9_jNF<br />
k`N "q# 9g@ #gF ##" #"j<br />
`_0q_ #"q_ _&"9p_ _g"`L_ _*"# jAF,'<br />
9# "b_j "b_ g" *g _gF 9_ g#" "L_*"qNF<br />
"b_ "#_ "NL _B# _I@ j#" _#"<br />
NM_0"*g_ j""9u_ gP q_ _w@ ]_ _g*"F_g@<br />
"NNh_ !w#_ 9#g" "m*" _#*" _dN@"<br />
9##g_0@q__ #"4_ j*"k __*NF_g#@P"<br />
"9NN#gIPNL_ "b@" _2M"Lg#N@F"<br />
""P@*NN#gEZgNN@#@P""</nowiki>=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
''The milestones that I anticipate are:''<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158911OWASP Hive Project2013-09-23T19:44:00Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
__gggrgM**M#mggg__<br />
__wgNN@"B*P""mp""@d#"@N#Nw__<br />
_g#@0F_a*F# _*F9m_ ,F9*__9NG#g_<br />
_mN#F aM" #p" !q@ 9NL "9#Qu_<br />
g#MF _pP"L _g@"9L_ _g""#__ g"9w_ 0N#p<br />
_0F jL*" 7_wF #_gF 9gjF "bJ 9h_<br />
j# gAF _@NL WELCOME J@u_ 2#_ #_<br />
,FF_#" 9_ _#" "b_ g@ "hg _#" !q_ jF "*_09_<br />
F N" #p" Ng@ TO `#g" "w@ "# t<br />
j p# g"9_ g@"9_ gP"#_ gF"q Pb L<br />
0J k _@ 9g_ j#" "b_ j#" "b_ _d" q_ g ##<br />
#F `NF "#g" THE "Md" GRID 5N# 9W" j#<br />
#k jFb_ g@"q_ _*"9m_ _*"R_ _#Np J#<br />
tApjF 9g J" 9M_ _m" 9%_ _*" "# gF 9_jNF<br />
k`N "q# 9g@ #gF ##" #"j<br />
`_0q_ #"q_ _&"9p_ _g"`L_ _*"# jAF,'<br />
9# "b_j "b_ g" *g _gF 9_ g#" "L_*"qNF<br />
"b_ "#_ "NL _B# _I@ j#" _#"<br />
NM_0"*g_ j""9u_ gP q_ _w@ ]_ _g*"F_g@<br />
"NNh_ !w#_ 9#g" "m*" _#*" _dN@"<br />
9##g_0@q__ #"4_ j*"k __*NF_g#@P"<br />
"9NN#gIPNL_ "b@" _2M"Lg#N@F"<br />
""P@*NN#gEZgNN@#@P""<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
''The milestones that I anticipate are:''<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=158910OWASP GSD Project2013-09-23T19:41:31Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$2000<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone Cluster''' - Cost for 10 Environment Hive 600.00 (Approx) <br />
*** '''4gb miniSD Card''' - Cost 12.37 (per BB) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per BB)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''UPDATE'''<br />
** The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret!<br />
** Temp introducer URL <br />
** ''' pb://o2fmouklqr72hnvdmk7rwu476bgbt2qf@tahoe.netgreen.us:35394,127.0.0.1:35394/introducer '''<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158909OWASP Hive Project2013-09-23T19:38:09Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
''The milestones that I anticipate are:''<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158908OWASP Hive Project2013-09-23T19:37:33Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
The milestones that I anticipate are:<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID.<br />
[https://tahoe-lafs.org Tahoe-lafs homepage]<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158907OWASP Hive Project2013-09-23T19:35:58Z<p>Jason Johnson: </p>
<hr />
<div>== '''WELCOME TO THE GRID'''==<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
The milestones that I anticipate are:<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID. <br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158906OWASP Hive Project2013-09-23T19:35:13Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
<nowiki>URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3</nowiki><br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
The milestones that I anticipate are:<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID. <br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=158905OWASP Hive Project2013-09-23T19:34:24Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
<br />
=What is it?=<br />
The HIVE project started out as an idea for a learning platform. Using TAHOE-lafs as a storage solution we are able to interlock anything we do into the GRID. What’s the GRID? The GRID is a group of Tahoe enabled capable computers (The BeagleBone Black) could be any computer. The idea is to share data across a GRID in a secure anonymous fashion. Using Tahoe-LAFS we can share and distribute project files lots and lots of data all gathered from the GRID. This uses “provider-independent security” that means I don’t know what your data is and neither does anyone else. Only you know what you uploaded so unless someone beats you with sticks until you hand over you unique URI. It’s all secret! URI looks something like <br />
<br />
URI%3ACHK%3Am6wj5avuhim3flsd2w54lhjcke:j2njlm3cm4sjzqdiwbadmts35lxa656kpvo66kx7wtlfyr6cab6a:3:10:3<br />
<br />
Currently I am using a 3 to 10 ratio that means you will need at least 3 storage nodes to retrieve files from in order to download your erasure encoded stuff. There are two kinds of files: immutable and mutable. When you upload a file to the storage grid you can choose which kind of file it will be in the grid. Immutable files can't be modified once they have been uploaded. A mutable file can be modified by someone with read-write access to it. A user can have read-write access to a mutable file or read-only access to it, or no access to it at all. If you want more details the link will take you to a site interactive illustration by Drew Perttula http://bigasterisk.com/tahoe-playground/<br />
<br />
Some ways I can see this being useful for OWASP is a HIVE cache that is currently what this project is becoming 10-1000 nodes strong but monitoring is controlled and nodes do what they please. The end goal is to provide a global grid for OWASP and any amount of users can use the GRID; a large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.<br />
<br />
Example of project based use. Let’s say BOB has a tomcat server and he wants to share its contents to JOE. BOB has Tahoe up and sets up a dropfolder and this folder he sets up just happens to be his entire tomcat folder. As files change they are sent to the grid and encrypted, stored and shared out to people that JOE selected to give his folder URI to. JOE now has a working copy of BOB’s stuff and can help or just create his own environment. All the while we always use SFTP or SSL with our frontends. If a node gets hacked and stolen because JACK forgot to lock up then big deal there are X number of nodes left and the files on JACKS node are encrypted erasure style. <br />
<br />
The milestones that I anticipate are:<br />
<br />
Sweet user interface<br />
Find a LCD for the BeagleBone Black for IP or stats scrolling.<br />
The HIVE setup currently shows the nodes in real time. (expand more on this) <br />
Make a proposal to OWASP for a more stable introducer and private GRID. <br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Code_Review_V2_Table_of_Contents&diff=153999OWASP Code Review V2 Table of Contents2013-06-17T17:09:56Z<p>Jason Johnson: </p>
<hr />
<div><br />
= '''OWASP Code Review Guide v2.0:''' =<br />
<br />
==Forward==<br />
# Author - Eoin Keary<br />
# Previous version to be updated:[[https://www.owasp.org/index.php/Code_Review_Guide_History]]<br />
'''[[CRV2_Forward|Content here]]'''<br />
<br />
== Code Review Guide Introduction==<br />
# Author - Eoin Keary<br />
# Previous version to be updated:[[https://www.owasp.org/index.php/Code_Review_Introduction]]<br />
'''[[CRV2_Introduction|Content here]]'''<br />
<br />
=== What is source code review and Static Analysis ===<br />
# Author - Zyad Mghazli<br />
# New Section<br />
''' [[CRV2_WhatIsCodeReview|Content here]]'''<br />
<br />
=== Manual Review - Pros and Cons ===<br />
# Author - Ashish Rao<br />
# New Section<br />
# Suggestion: Benchmark of different Stataic Analysis Tools Zyad Mghazli<br />
# Suggestion: Highlight the advantages of code review to the department/team - Gary David Robinson<br />
# [[CRV2_ManualReviewProsCons|Put content here]]<br />
<br />
=== Why code review ===<br />
==== Scope and Objective of secure code review ====<br />
# Author - Ashish Rao<br />
# [[CRV2_WhyCodeReview|Put content here]]<br />
<br />
=== We can't hack ourselves secure ===<br />
# Author - Prathamesh Mhatre<br />
# New Section<br />
# [[CRV2_CantHackSecure|Put content here]]<br />
<br />
=== 360 Review: Coupling source code review and Testing / Hybrid Reviews===<br />
# Author - Ashish Rao<br />
# New Section<br />
# [[CRV2_360Review|Put content here]]<br />
<br />
=== Can static code analyzers do it all? ===<br />
# Author - Ashish Rao<br />
# New Section<br />
# [[CRV2_CanStaticAnalyzersDoAll|Put content here]]<br />
<br />
=Methodology=<br />
===The code review approach===<br />
#Author - Prathamesh Mhatre<br />
# [[CRV2_CodeReviewApproach|Put content here]]<br />
<br />
==== Preparation and context ====<br />
# Author - Open<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Code_Review_Preparation]]<br />
# [[CRV2_PrepContext|Put content here]]<br />
<br />
====Application Threat Modeling====<br />
#Author - Andy, Renchie Joan<br />
# Previous version to be updated: [[https://www.owasp.org/OCRG1.1:Application_Threat_Modeling]]<br />
# [[CRV2_AppThreatModeling|Put content here]]<br />
<br />
====Understanding Code layout/Design/Architecture====<br />
#Author - Ashish Rao<br />
# [[CRV2_CodeLayoutDesignArch|Put content here]]<br />
<br />
===SDLC Integration===<br />
#Author - Andy, Ashish Rao<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Security_Code_Review_in_the_SDLC]]<br />
# [[CRV2_SDLCInt|Put content here]]<br />
<br />
====Deployment Models====<br />
=====Secure deployment configurations=====<br />
#Author - Ashish Rao<br />
# [[CRV2_SecDepConfig|Put content here]]<br />
<br />
# New Section<br />
=====Metrics and code review=====<br />
#Author - Andy<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Code_Review_Metrics]]<br />
# [[CRV2_MetricsCodeRev|Put content here]]<br />
<br />
=====Source and sink reviews=====<br />
#Author - Ashish Rao<br />
# New Section<br />
# [[CRV2_SourceSinkRev|Put content here]]<br />
<br />
=====Code review Coverage=====<br />
#Author - Open<br />
#Previous version to be updated: [[https://www.owasp.org/index.php/Code_Review_Coverage]]<br />
# [[CRV2_CodeRevCoverage|Put content here]]<br />
<br />
=====Design Reviews=====<br />
#Author - Ashish Rao<br />
*Why to review design?<br />
**Building security in design - secure by design principle<br />
**Design Areas to be reviewed<br />
**Common Design Flaws<br />
# [[CRV2_DesignRev|Put content here]]<br />
<br />
=====A Risk based approach to code review=====<br />
#Author - Renchie Joan<br />
#New Section<br />
*"Doing things right or doing the right things..."<br />
**"Not all bugs are equal<br />
# [[CRV2_RiskBasedApproach|Put content here]]<br />
<br />
====Crawling code====<br />
#Author - Abbas Naderi<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Crawling_Code]]<br />
*API of Interest:<br />
**Java<br />
**.NET<br />
**PHP<br />
**RUBY<br />
*Frameworks:<br />
**Spring<br />
**.NET MVC<br />
**Structs<br />
**Zend<br />
#New Section<br />
*Searching for code in C/C++<br />
#Author - Gary Robinson<br />
<br />
# [[CRV2_CrawlingCode|Put content here]]<br />
<br />
====Code reviews and Compliance====<br />
#Author -Manual Harti<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Code_Reviews_and_Compliance]]<br />
# [[CRV2_CodeRevCompliance|Put content here]]<br />
<br />
=Reviewing by Techincal Control=<br />
===Reviewing code for Authentication controls===<br />
#Author - Anand Prakash, Joan Renchie<br />
# [[CRV2_AuthControls|Put content here]]<br />
<br />
====Forgot password====<br />
#Author Abbas Naderi<br />
# [[CRV2_ForgotPassword|Put content here]]<br />
<br />
====Authentication====<br />
#Author - Anand Prakash, Joan Renchie<br />
# [[CRV2_Authentication|Put content here]]<br />
<br />
====CAPTCHA====<br />
#Author Larry Conklin, Joan Renchie<br />
'''[[CRV2_CAPTCHA|Content here]]'''<br />
<br />
====Out of Band considerations====<br />
#Author - Open<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Authentication]]<br />
# [[CRV2_OutofBand|Put content here]]<br />
<br />
===Reviewing code Authorization weakness===<br />
#Author Ashish Rao<br />
# [[CRV2_AuthorizationWeaknesses|Put content here]]<br />
<br />
====Checking authz upon every request====<br />
#Author - Abbas Naderi, Joan Renchie<br />
# [[CRV2_CheckAuthzEachRequest|Put content here]]<br />
<br />
====Reducing the attack surface====<br />
#Author Chris Berberich<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Authorization]]<br />
# [[CRV2_ReducingAttSurf|Put content here]]<br />
<br />
====Reviewing code for Session handling====<br />
#Author - Palak Gohil, Abbas Naderi<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Session-Management]]<br />
# [[CRV2_SessionHandling|Put content here]]<br />
<br />
====Reviewing client side code====<br />
#New Section<br />
# [[CRV2_ClientSideCodeIntro|Put content here]]<br />
<br />
=====Javascript=====<br />
#Author - Abbas Naderi<br />
# [[CRV2_ClientSideCodeJScript|Put content here]]<br />
<br />
=====JSON=====<br />
#Author - Open<br />
# [[CRV2_ClientSideCodeJSon|Put content here]]<br />
<br />
=====Content Security Policy=====<br />
#Author - Open<br />
# [[CRV2_ClientSideCodeContSecPolicy|Put content here]]<br />
<br />
====="Jacking"/Framing=====<br />
#Author - Abbas Naderi<br />
# [[CRV2_ClientSideCodeJackingFraming|Put content here]]<br />
<br />
=====HTML 5?=====<br />
#Author - Sebastien Gioria<br />
# [[CRV2_ClientSideCodeHTML5|Put content here]]<br />
<br />
=====Browser Defenses policy=====<br />
#Author - Open<br />
# [[CRV2_ClientSideCodeBrowserDefPol|Put content here]]<br />
<br />
=====etc...=====<br />
<br />
====Review code for input validation====<br />
#Author - Open<br />
# [[CRV2_InputValIntro|Put content here]]<br />
<br />
=====Regex Gotchas=====<br />
#Author - Abbas Naderi<br />
#New Section<br />
# [[CRV2_InputValRegexGotchas|Put content here]]<br />
<br />
=====ESAPI=====<br />
#Author - Abbas Naderi<br />
#New Section<br />
# Internal Link: [[https://www.owasp.org/index.php/Codereview-Input_Validation]]<br />
# [[CRV2_InputValESAPI|Put content here]]<br />
<br />
====Reviewing code for contextual encoding====<br />
=====HTML Attribute=====<br />
#Author - Shenai Silva<br />
# [[CRV2_ContextEncHTMLAttribute|Put content here]]<br />
<br />
=====HTML Entity=====<br />
#Author - Shenai Silva<br />
# [[CRV2_ContextEncHTMLEntity|Put content here]]<br />
<br />
=====Javascript Parameters=====<br />
#Author - Open<br />
# [[CRV2_ContextEncJscriptParams|Put content here]]<br />
<br />
=====JQuery=====<br />
#Author - Abbas Naderi<br />
# [[CRV2_ContextEncJQuery|Put content here]]<br />
<br />
====Reviewing file and resource handling code====<br />
#Author - Open<br />
# [[CRV2_FileResourceHandling|Put content here]]<br />
<br />
====Resource Exhaustion - error handling====<br />
#Author - Abbas Naderi<br />
# [[CRV2_ResourceExhaustionErrHandling|Put content here]]<br />
<br />
=====native calls=====<br />
#Author Abbas Naderi<br />
# [[CRV2_ResourceExhaustionNativeCalls|Put content here]]<br />
<br />
====Reviewing Logging code - Detective Security====<br />
#Author - Palak Gohil<br />
* Where to Log<br />
* What to log<br />
* What not to log<br />
* How to log<br />
# Internal link: [[https://www.owasp.org/index.php/Logging_Cheat_Sheet]]<br />
# [[CRV2_LoggingCode|Put content here]]<br />
<br />
====Reviewing Error handling and Error messages====<br />
#Author - Gary Robinson<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Error-Handling]]<br />
# [[CRV2_ErrorHandlingMessages|Put content here]]<br />
<br />
====Reviewing Security alerts====<br />
#Author - Open<br />
# [[CRV2_SecurityAlerts|Put content here]]<br />
<br />
====Review for active defense====<br />
#Author - Colin Watson<br />
# [[CRV2_ActiveDefense|Put content here]]<br />
<br />
====Reviewing Secure Storage====<br />
#Author - Azzeddine Ramrami<br />
# New Section<br />
# [[CRV2_SecureStorage|Put content here]]<br />
<br />
====Hashing & Salting - When, How and Where====<br />
=====Encrpyption=====<br />
======.NET======<br />
#Author Larry Conklin, Joan Renchie<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Cryptographic_Controls]]<br />
*''Can we talk about key storage as well i.e. key management for encryption techniques used in the application? - Ashish Rao''<br />
'''[[CRV2_HashingandSaltingdotNet|Content here]]'''<br />
<br />
=Reviewing by Vulnerability=<br />
===Review Code for XSS===<br />
#Author Palak Gohil, Anand Prakash<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Reviewing_Code_for_Cross-Site_Scripting]]<br />
# In reviewing code for XSS - we can give more patterns on "source to sink" patterns for ASP.NET wrf to difference versions and mechanisms to display data in a page - Ashish Rao<br />
# [[CRV2_RevCodeXSS|Put content here]]<br />
<br />
===Persistent - The Anti pattern===<br />
#Author Abbas Naderi<br />
# [[CRV2_RevCodePersistentAntiPatternIntro|Put content here]]<br />
<br />
====.NET====<br />
#Author Johanna Curiel, Renchie Joan, Larry Conklin<br />
# [[CRV2_RevCodePersistentAntiPatterndotNet|Put content here]]<br />
<br />
====.Java====<br />
#Author Palak Gohil<br />
# [[CRV2_RevCodePersistentAntiPatternJava|Put content here]]<br />
<br />
====PHP====<br />
#Author Mohammed Damavandi, Abbas Naderi<br />
# [[CRV2_RevCodePersistentAntiPatternPHP|Put content here]]<br />
<br />
====Ruby====<br />
#Author Chris Berberich<br />
# [[CRV2_RevCodePersistentAntiPatternRuby|Put content here]]<br />
<br />
===Reflected - The Anti pattern===<br />
# [[CRV2_RevCodeReflectedAntiPatternIntro|Put content here]]<br />
<br />
====.NET====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_RevCodeReflectedAntiPatterndotNet|Put content here]]<br />
<br />
====.Java====<br />
#Author Palak Gohil<br />
# [[CRV2_RevCodeReflectedAntiPatternJava|Put content here]]<br />
<br />
====PHP====<br />
#Author Mohammed Damavandi, Abbas Naderi<br />
# [[CRV2_RevCodeReflectedAntiPatternPHP|Put content here]]<br />
<br />
====Ruby====<br />
# Author - Open<br />
# [[CRV2_RevCodeReflectedAntiPatternIRuby|Put content here]]<br />
<br />
===Stored - The Anti pattern===<br />
# Author - Open<br />
# [[CRV2_RevCodeStoredAntiPatternIntro|Put content here]]<br />
<br />
====.NET====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_RevCodeStoredAntiPatterndotNET|Put content here]]<br />
<br />
====.Java====<br />
#Author Palak Gohil<br />
# [[CRV2_RevCodeStoredAntiPatternJava|Put content here]]<br />
<br />
====PHP====<br />
#Author Mohammed Damavandi, Abbas Naderi<br />
# [[CRV2_RevCodeStoredAntiPatternPHP|Put content here]]<br />
<br />
====Ruby====<br />
#Author - Open<br />
# [[CRV2_RevCodeStoredAntiPatternRuby|Put content here]]<br />
<br />
===DOM XSS ===<br />
#Author Larry Conklin<br />
# [[CRV2_DOMXSS|Put content here]]<br />
<br />
===JQuery mistakes===<br />
#Author Shenal Silva<br />
# [[CRV2_JQueryMistakes|Put content here]]<br />
<br />
===Reviewing code for SQL Injection===<br />
#Author Palak Gohil, Renchie Joan<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Reviewing_Code_for_SQL_Injection]]<br />
# [[CRV2_RevCodeSQLInjection|Put content here]]<br />
<br />
====PHP====<br />
#Author - Mennouchi Islam Azeddine<br />
# [[CRV2_SQLInjPHP|Put content here]]<br />
<br />
====Java====<br />
#Author - Open<br />
# [[CRV2_SQLInjJava|Put content here]]<br />
<br />
====.NET====<br />
#Author - Mennouchi Islam Azeddine<br />
# [[CRV2_SQLInjdotNET|Put content here]]<br />
<br />
====HQL====<br />
#Author - Open<br />
# [[CRV2_SQLInjHQL|Put content here]]<br />
<br />
===The Anti pattern===<br />
#Author Larry Conklin<br />
#[[CRV2_AntiPattern| Content here]]<br />
https://www.owasp.org/index.php/CRV2_AntiPattern<br />
====PHP====<br />
#Author - Mohammad Damavandi, Abbas Naderi<br />
# [[CRV2_AntiPatternPHP|Put content here]]<br />
<br />
====Java====<br />
#Author - Palak Gohil<br />
#=> Searching for traditional SQL,JPA,JPSQL,Criteria,...<br />
# [[CRV2_AntiPatternJava|Put content here]]<br />
<br />
====.NET====<br />
#Author Johanna Curiel, Renchie Joan,Larry Conklin<br />
# [[CRV2_AntiPatterndotNet|Put content here]]<br />
<br />
====Ruby====<br />
#Author - Open<br />
# [[CRV2_AntiPatternRuby|Put content here]]<br />
<br />
====Cold Fusion====<br />
#Author - Open<br />
# [[CRV2_AntiPatternColdFusion|Put content here]]<br />
<br />
===Reviewing code for CSRF Issues===<br />
#Author Palak Gohil,Anand Prakash, Abbas Naderi<br />
# Previous version to be updated: [[https://www.owasp.org/index.php/Reviewing_Code_for_Cross-Site_Request_Forgery]]<br />
# [[CRV2_CSRFIssues|Put content here]]<br />
<br />
===Transactional logic / Non idempotent functions / State Changing Functions===<br />
#Author Abbas Naderi<br />
# [[CRV2_TransLogic|Put content here]]<br />
<br />
===Reviewing code for poor logic /Business logic/Complex authorization===<br />
#Author - Sam Denard<br />
# [[CRV2_PoorLogic|Put content here]]<br />
<br />
===Reviewing Secure Communications===<br />
====.NET Config====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_SecCommsdotNet|Put content here]]<br />
<br />
====Spring Config====<br />
#Author - Open<br />
# [[CRV2_SecCommsSpringConfig|Put content here]]<br />
<br />
====HTTP Headers====<br />
#Author Gregory Disney, Abbas Naderi<br />
# [[CRV2_SecCommsHTTPHdrs|Put content here]]<br />
<br />
=====CSP=====<br />
#Author Gregory Disney<br />
# [[CRV2_SecCommsHTTPHdrsCSP|Put content here]]<br />
<br />
=====HSTS=====<br />
#Author Abbas Naderi<br />
# [[CRV2_SecCommsHTTPHSTS|Put content here]]<br />
<br />
===Tech-Stack pitfalls===<br />
#Author Gregory Disney<br />
# [[CRV2_TechStackPitfalls|Put content here]]<br />
<br />
===Framework specific Issues===<br />
====Spring====<br />
#Author - Open<br />
# [[CRV2_FrameworkSpecIssuesSpring|Put content here]]<br />
<br />
====Structs====<br />
#Author - Open<br />
# [[CRV2_FrameworkSpecIssuesStructs|Put content here]]<br />
<br />
====Drupal====<br />
#Author Gregory Disney<br />
# [[CRV2_FrameworkSpecIssuesDurpal|Put content here]]<br />
<br />
====Ruby on Rails====<br />
#Author - Open<br />
# [[CRV2_FrameworkSpecIssuesROR|Put content here]]<br />
<br />
====Django====<br />
#Author Gregory Disney<br />
# [[CRV2_FrameworkSpecIssuesDjango|Put content here]]<br />
<br />
====.NET Security / MVC====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesdotNetMVC|Put content here]]<br />
<br />
====Security in ASP.NET applications====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesASPNet|Put content here]]<br />
<br />
=====Strongly Named Assemblies=====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesASPNetStrongAssembiles|Put content here]]<br />
<br />
======Round Tripping======<br />
# Author - Open<br />
# [[CRV2_FrameworkSpecIssuesASPNetRT|Put content here]]<br />
<br />
======How to prevent Round tripping======<br />
# Author - Open<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesASPNetRTPrevention|Put content here]]<br />
<br />
=====Setting the right Configurations=====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesASPNetConfigs|Put content here]]<br />
<br />
=====Authentication Options=====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesASPNetAuth|Put content here]]<br />
<br />
=====Code Review for Managed Code - .Net 1.0 and up=====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesASPNetManagedCode|Put content here]]<br />
<br />
=====Using OWASP Top 10 as your guideline=====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesASPTop10|Put content here]]<br />
<br />
=====Code review for Unsafe Code (C#)=====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesASPNetUnsafeCode|Put content here]]<br />
<br />
====PHP Specific Issues====<br />
#Author Mohammad Damavandi, Abbas Naderi<br />
# [[CRV2_FrameworkSpecIssuesPHP|Put content here]]<br />
<br />
====Classic ASP====<br />
#Author Johanna Curiel<br />
# [[CRV2_FrameworkSpecIssuesASPClassic|Put content here]]<br />
<br />
====C#====<br />
#Author Johanna Curiel, Renchie Joan<br />
# [[CRV2_FrameworkSpecIssuesCsharp|Put content here]]<br />
<br />
====C/C++====<br />
#Author Gary Robinson<br />
# [[CRV2_FrameworkSpecIssuesCplusplus|Put content here]]<br />
<br />
====Objective C====<br />
#Author Open<br />
# [[CRV2_FrameworkSpecIssuesObectiveC|Put content here]]<br />
<br />
====Java====<br />
#Author Palak Gohil<br />
# [[CRV2_FrameworkSpecIssuesJava|Put content here]]<br />
<br />
====Android====<br />
#Author Open<br />
# [[CRV2_FrameworkSpecIssuesAndroid|Put content here]]<br />
<br />
====Coldfusion====<br />
#Author Open<br />
# [[CRV2_FrameworkSpecIssuesColdfusion|Put content here]]<br />
<br />
=Security code review for Agile development=<br />
#Author Open<br />
# [[CRV2_CodeReviewAgile|Put content here]]<br />
<br />
=Willing to review drafts=<br />
#Terry Nerpester<br />
#Larry Conklin<br />
#Gary Robinson<br />
#Simon Whittaker<br />
#Jason Johnson</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=153624OWASP Hive Project2013-06-13T19:24:55Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
<br />
=What is it?=<br />
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone Cluster''' - Cost for 10 Environment Hive 600.00 (Approx) <br />
*** '''4gb miniSD Card''' - Cost 12.37 (per BB) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per BB)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=153623OWASP GSD Project2013-06-13T19:23:50Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$0 (soon to be $2,000 (once the payment for SI's 2013 membership goes through)<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone Cluster''' - Cost for 10 Environment Hive 600.00 (Approx) <br />
*** '''4gb miniSD Card''' - Cost 12.37 (per BB) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per BB)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_GSD_Project&diff=153622OWASP GSD Project2013-06-13T19:22:44Z<p>Jason Johnson: </p>
<hr />
<div>OWASP GSD (Get Stuff Done) project is focused on enabling and empowering other OWASP Projects with funds, resources, energy and ideas.<br />
<br />
The first initiative is the 'Funds Available for OWASP Projects' (see details and rules-of-engagement below)<br />
<br />
* Project Leader: Dinis Cruz<br />
* Proposals Review Team: Dennis Groves, Daniel Cuthbert, Dinis Cruz (contact Dinis If want to be one)<br />
<br />
== Initiative: Funds Available for OWASP Projects==<br />
<br />
'''What:''' OWASP Project Sponsorship model where OWASP Leaders can spend up-to the current allocated budget on OWASP Projects<br />
<br />
'''Rules-of-Engagement:'''<br />
<br />
* Funds are to be used on OWASP Projects<br />
* Funds to be personally allocated by an OWASP Leader (who takes responsibility for its use and execution)<br />
* OWASP leaders are free to spend the funds on OWASP Projects in anyway they feel relevant, with only the following KEY restrictions:<br />
** They can't pay another OWASP leaders or a company that an OWASP leader is directly connected to<br />
** For amounts less than $500 they add its description to the respective OWASP WIKI page 24h before they commit to make the expense<br />
** For amounts less than $5000 they add its description to the respective OWASP WIKI 7 days before they commit to make the expense<br />
** If there are no comments or objections by the 'Proposals Review Team', the funds are automatically approved<br />
** If a member of the 'Proposals Review Team' objects or asks for more information, the funds are NOT approved (until further clarifications)<br />
*Each expense item is mapped to an individual OWASP leader and multiple OWASP Leaders can work together.<br />
*Payments will be made by Alison on Invoice submission (by paypal or direct bank transfer)<br />
<br />
In 6 months time, a review of the outcomes will be done and see these rules need to be changed<br />
<br />
===Funds Sources===<br />
<br />
* Total: 2000 USD (soon to be 4000 USD)<br />
* Sponsors: (could be OWASP Chapters, OWASP Members or 3rd party companies/organizations)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2012)<br />
** [http://securityinnovation.com/ Security Innovation] - $2000 allocated from OWASP Corporate membership (2013)<br />
<br />
===Proposed Use of Funds Available ===<br />
<br />
'''Current Fund Amount'''<br />
<br />
*$0 (soon to be $2,000 (once the payment for SI's 2013 membership goes through)<br />
<br />
'''Active Projects using GSD funds (1):'''<br />
*'''OWASP HIVE PROJECT''' - <br />
** Funds allocated: $1764.95<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone Cluster''' - Cost for 10 Environment Hive 600.00 (Approx) <br />
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single OWASPi HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per BB)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
'''Completed:''' <br />
*'''Transcription of Podcast''' - Total Cost: $70 USD (Approx)<br />
* '''Transcribe OWASP Board Member candidates interview.''' <br />
** contracted via Elance ([https://www.elance.com/j/transcribe-audio-interviews/33455435/ see proposal here]) <br />
** Cost: $92.05 USD<br />
** '''O2 Platform Stickers''' - Total Cost: $73.00 USD (Approx)<br />
<br />
===FAQ===<br />
<br />
For Participants:<br />
<br />
* '''What is an OWASP Leader?''' : Everybody in the owasp-leaders list<br />
* '''Can these funds be used on other OWASP innitiatives (Chapters, Conferences, Summits, etc..)''' : Nope this is only for OWASP Projects<br />
* ''' What happens if the 'Proposals Review Team' objects or asks questions''' : The OWASP Leader behind the proposal needs to come back with a better idea or answer :)<br />
* '''Is there some kind of '[http://en.wikipedia.org/wiki/Gamification Gamification] theory' behind this idea?''' : Yes :)<br />
<br />
<br />
For Members of the 'Proposals Review Team':<br />
<br />
* '''What should I do if I like a proposal?''' : Nothing (unless you have time to help that proposal). Note that proposals with no 'doubts' are approved by default<br />
* '''What should I do if I have doubts about a proposal?''' : Write a comment and raise your doubts/questions. Note that proposals with (at least one ) 'doubt' comment and NOT approved by default<br />
<br />
===GSD Ideas===<br />
Here are a couple ideas on where to use available GSD funds:<br />
<br />
* buy 20 copies of the (for example) Open SAMM book and distribute it at a local OWASP chapter meeting<br />
* support the OWASP Developer Guide and ASVS projects (for example with copywriting, formatting, design, research, proof-reading, pagination, etc...)<br />
* improve the formatting and presentation of the 'Cheat-Sheet' series,<br />
* hire a transcription service for key presentations done at OWASP chapters/events (or OWASP PodCasts)<br />
* create a DVD with all presentations from a specific OWASP event (or other video materials like the AppSec tutorial series)<br />
* sponsor a booth at an event to present OWASP Projects<br />
* sponsor travel expenses for a project leader to meet with other project leaders or collaborators (to work on a particular project)<br />
* organize a mini-summit around an OWASP project<br />
* create a mini-website focused on a particular project (like ESAPI.org) <br />
* try out a specific commercial service that will make a particular project more effective (version control, bug tracking system, mailing lists, etc...)<br />
* hire designers to work on OWASP projects<br />
* translate OWASP content (to and from English)<br />
* sponsor students to work on OWASP projects (maybe even run a mini-OWASP Season of Code)<br />
* hire mediawiki editors for the OWASP website (the OWASP projects part of it :) )<br />
* etc...<br />
<br />
__NOTOC__</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=153621OWASP Hive Project2013-06-13T19:21:24Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
<br />
=What is it?=<br />
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone Cluster''' - Cost for 10 Environment Hive 600.00 (Approx) <br />
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single OWASPi HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per BB)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.newark.com/jsp/search/productdetail.jsp?sku=65W6016 element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=153620OWASP Hive Project2013-06-13T19:18:52Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
<br />
=What is it?=<br />
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''<br />
** ''' Cost Breakdown '''<br />
*** '''BeagleBone Cluster''' - Cost for 10 Environment Hive 600.00 (Approx) <br />
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single OWASPi HIVE-OFF''' - Cost 60.00 - 85.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per BB)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.element14.com/community/groups/raspberry-pi element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=File:Owaspi.png&diff=153619File:Owaspi.png2013-06-13T19:16:30Z<p>Jason Johnson: uploaded a new version of &quot;File:Owaspi.png&quot;: Better design</p>
<hr />
<div></div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=Projects/OWASP_Hive_Project&diff=153349Projects/OWASP Hive Project2013-06-10T20:34:27Z<p>Jason Johnson: </p>
<hr />
<div>{{Template:Project About<br />
| project_name =OWASP_Hive_Project<br />
| project_home_page =OWASP_Hive_Project<br />
| project_description = The HIVE is a bunch of PI's in a cluster or stand alone. The SANDBOX! <br />
'''hive''' (noun)<br />
;1. THE HIVE <br />
:a. Structure for housing bees aka (WASPS), especially owasps.<br />
:b. Colony of bees/owasps living in such a structure.<br />
:2. A place swarming with activity.<br />
:v. hived, hiv·ing, hives <br />
:'''1. To collect into a hive.'''<br />
:'''2. To store (data) in a hive.'''<br />
:'''3. To store up; accumulate.'''<br />
:v.intr.<br />
:1. To enter and occupy a hive or network.<br />
:2. To live with many others in close association (OWASP).<br />
;Phrasal Verb: <br />
:'''hive off (term used when gathering)'''<br />
:To set apart from a group: hived off the department into another division.<br />
| leader_name1 =Jason Johnson<br />
| leader_email1 =Jason.Johnson@owasp.org <br />
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp_hive_project<br />
| project_road_map = https://www.owasp.org/index.php/Projects/OWASP_Hive_Project/Roadmap<br />
| presentation_link = http://prezi.com/ffc3mt-f8jd6/untitled-prezi/?utm_campaign=share&utm_medium=copy<br />
}}</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=Projects/OWASP_Hive_Project&diff=153348Projects/OWASP Hive Project2013-06-10T20:33:50Z<p>Jason Johnson: </p>
<hr />
<div>{{Template:Project About<br />
| project_name =OWASP_Hive_Project<br />
| project_home_page =OWASP_Hive_Project<br />
| project_description = The HIVE is a bunch of PI's in a cluster or stand alone. The SANDBOX! <br />
'''hive''' (noun)<br />
;1. THE HIVE <br />
:a. Structure for housing bees aka (WASPS), especially owasps.<br />
:b. Colony of bees/owasps living in such a structure.<br />
:2. A place swarming with activity.<br />
:v. hived, hiv·ing, hives <br />
:'''1. To collect into a hive.'''<br />
:'''2. To store (data) in a hive.'''<br />
:'''3. To store up; accumulate.'''<br />
:v.intr.<br />
:1. To enter and occupy a hive or network.<br />
:2. To live with many others in close association (OWASP).<br />
;Phrasal Verb: <br />
:'''hive off (term used when gathering)'''<br />
:To set apart from a group: hived off the department into another division.<br />
| leader_name1 =Jason Johnson<br />
| leader_email1 =Jason.Johnson@owasp.org <br />
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp_hive_project<br />
| project_road_map = https://www.owasp.org/index.php/Projects/OWASP_Hive_Project/Roadmap<br />
| presentation_link = <br />
}}</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=Template:Project_About&diff=153347Template:Project About2013-06-10T20:31:45Z<p>Jason Johnson: </p>
<hr />
<div><includeonly><br />
{|border="0" cellpadding="2" cellspacing="3"<br />
!width="50%" style="background:white;" | PROJECT INFO<br> <small>''What does this OWASP project offer you?''</small><br />
!width="50%" style="background:white;" | RELEASE(S) INFO<br> <small>''What releases are available for this project?''</small><br />
|-<br />
|valign="top"|{{Template:Project Info<br />
| project_name = {{#if: {{{project_name|}}} | {{{project_name}}} | }}<br />
| project_home_page = {{#if: {{{project_home_page|}}} | {{{project_home_page}}} | }}<br />
| project_description = {{#if: {{{project_description|}}} | {{{project_description}}} | }}<br />
| project_license = {{#if: {{{project_license|}}} | {{{project_license}}} | }}<br />
| leader_name1 = {{#if: {{{leader_name1|}}} | {{{leader_name1}}} | }}<br />
| leader_email1 = {{#if: {{{leader_email1|}}} | {{{leader_email1}}} | }}<br />
| leader_username1 = {{#if: {{{leader_username1|}}} | {{{leader_username1}}} | }}<br />
| leader_name2 = {{#if: {{{leader_name2|}}} | {{{leader_name2}}} | }}<br />
| leader_email2 = {{#if: {{{leader_email2|}}} | {{{leader_email2}}} | }}<br />
| leader_username2 = {{#if: {{{leader_username2|}}} | {{{leader_username2}}} | }}<br />
| leader_name3 = {{#if: {{{leader_name3|}}} | {{{leader_name3}}} | }}<br />
| leader_email3 = {{#if: {{{leader_email3|}}} | {{{leader_email3}}} | }}<br />
| leader_username3 = {{#if: {{{leader_username3|}}} | {{{leader_username3}}} | }}<br />
| leader_name4 = {{#if: {{{leader_name4|}}} | {{{leader_name4}}} | }}<br />
| leader_email4 = {{#if: {{{leader_email4|}}} | {{{leader_email4}}} | }}<br />
| leader_username4 = {{#if: {{{leader_username4|}}} | {{{leader_username4}}} | }}<br />
| leader_name5 = {{#if: {{{leader_name5|}}} | {{{leader_name5}}} | }}<br />
| leader_email5 = {{#if: {{{leader_email5|}}} | {{{leader_email5}}} | }}<br />
| leader_username5 = {{#if: {{{leader_username5|}}} | {{{leader_username5}}} | }}<br />
| leader_name6 = {{#if: {{{leader_name6|}}} | {{{leader_name6}}} | }}<br />
| leader_email6 = {{#if: {{{leader_email6|}}} | {{{leader_email6}}} | }}<br />
| leader_username6 = {{#if: {{{leader_username6|}}} | {{{leader_username6}}} | }}<br />
| leader_name7 = {{#if: {{{leader_name7|}}} | {{{leader_name7}}} | }}<br />
| leader_email7 = {{#if: {{{leader_email7|}}} | {{{leader_email7}}} | }}<br />
| leader_username7 = {{#if: {{{leader_username7|}}} | {{{leader_username7}}} | }}<br />
| leader_name8 = {{#if: {{{leader_name8|}}} | {{{leader_name8}}} | }}<br />
| leader_email8 = {{#if: {{{leader_email8|}}} | {{{leader_email8}}} | }}<br />
| leader_username8 = {{#if: {{{leader_username8|}}} | {{{leader_username8}}} | }}<br />
| leader_name9 = {{#if: {{{leader_name9|}}} | {{{leader_name9}}} | }}<br />
| leader_email9 = {{#if: {{{leader_email9|}}} | {{{leader_email9}}} | }}<br />
| leader_username9 = {{#if: {{{leader_username9|}}} | {{{leader_username9}}} | }}<br />
| leader_name10 = {{#if: {{{leader_name10|}}} | {{{leader_name10}}} | }}<br />
| leader_email10 = {{#if: {{{leader_email10|}}} | {{{leader_email10}}} | }}<br />
| leader_username10 = {{#if: {{{leader_username10|}}} | {{{leader_username10}}} | }}<br />
| maintainer_name1 = {{#if: {{{maintainer_name1|}}} | {{{maintainer_name1}}} | }}<br />
| maintainer_email1 = {{#if: {{{maintainer_email1|}}} | {{{maintainer_email1}}} | }}<br />
| maintainer_username1 = {{#if: {{{maintainer_username1|}}} | {{{maintainer_username1}}} | }}<br />
| maintainer_name2 = {{#if: {{{maintainer_name2|}}} | {{{maintainer_name2}}} | }}<br />
| maintainer_email2 = {{#if: {{{maintainer_email2|}}} | {{{maintainer_email2}}} | }}<br />
| maintainer_username2 = {{#if: {{{maintainer_username2|}}} | {{{maintainer_username2}}} | }}<br />
| maintainer_name3 = {{#if: {{{maintainer_name3|}}} | {{{maintainer_name3}}} | }}<br />
| maintainer_email3 = {{#if: {{{maintainer_email3|}}} | {{{maintainer_email3}}} | }}<br />
| maintainer_username3 = {{#if: {{{maintainer_username3|}}} | {{{maintainer_username3}}} | }}<br />
| maintainer_name4 = {{#if: {{{maintainer_name4|}}} | {{{maintainer_name4}}} | }}<br />
| maintainer_email4 = {{#if: {{{maintainer_email4|}}} | {{{maintainer_email4}}} | }}<br />
| maintainer_username4 = {{#if: {{{maintainer_username4|}}} | {{{maintainer_username4}}} | }}<br />
| maintainer_name5 = {{#if: {{{maintainer_name5|}}} | {{{maintainer_name5}}} | }}<br />
| maintainer_email5 = {{#if: {{{maintainer_email5|}}} | {{{maintainer_email5}}} | }}<br />
| maintainer_username5 = {{#if: {{{maintainer_username5|}}} | {{{maintainer_username5}}} | }}<br />
| maintainer_name6 = {{#if: {{{maintainer_name6|}}} | {{{maintainer_name6}}} | }}<br />
| maintainer_email6 = {{#if: {{{maintainer_email6|}}} | {{{maintainer_email6}}} | }}<br />
| maintainer_username6 = {{#if: {{{maintainer_username6|}}} | {{{maintainer_username6}}} | }}<br />
| maintainer_name7 = {{#if: {{{maintainer_name7|}}} | {{{maintainer_name7}}} | }}<br />
| maintainer_email7 = {{#if: {{{maintainer_email7|}}} | {{{maintainer_email7}}} | }}<br />
| maintainer_username7 = {{#if: {{{maintainer_username7|}}} | {{{maintainer_username7}}} | }}<br />
| maintainer_name8 = {{#if: {{{maintainer_name8|}}} | {{{maintainer_name8}}} | }}<br />
| maintainer_email8 = {{#if: {{{maintainer_email8|}}} | {{{maintainer_email8}}} | }}<br />
| maintainer_username8 = {{#if: {{{maintainer_username8|}}} | {{{maintainer_username8}}} | }}<br />
| maintainer_name9 = {{#if: {{{maintainer_name9|}}} | {{{maintainer_name9}}} | }}<br />
| maintainer_email9 = {{#if: {{{maintainer_email9|}}} | {{{maintainer_email9}}} | }}<br />
| maintainer_username9 = {{#if: {{{maintainer_username9|}}} | {{{maintainer_username9}}} | }}<br />
| maintainer_name10 = {{#if: {{{maintainer_name10|}}} | {{{maintainer_name10}}} | }}<br />
| maintainer_email10 = {{#if: {{{maintainer_email10|}}} | {{{maintainer_email10}}} | }}<br />
| maintainer_username10 = {{#if: {{{maintainer_username10|}}} | {{{maintainer_username10}}} | }}<br />
| contributor_name1 = {{#if: {{{contributor_name1|}}} | {{{contributor_name1}}} | }}<br />
| contributor_email1 = {{#if: {{{contributor_email1|}}} | {{{contributor_email1}}} | }}<br />
| contributor_username1 = {{#if: {{{contributor_username1|}}} | {{{contributor_username1}}} | }}<br />
| contributor_name2 = {{#if: {{{contributor_name2|}}} | {{{contributor_name2}}} | }}<br />
| contributor_email2 = {{#if: {{{contributor_email2|}}} | {{{contributor_email2}}} | }}<br />
| contributor_username2 = {{#if: {{{contributor_username2|}}} | {{{contributor_username2}}} | }}<br />
| contributor_name3 = {{#if: {{{contributor_name3|}}} | {{{contributor_name3}}} | }}<br />
| contributor_email3 = {{#if: {{{contributor_email3|}}} | {{{contributor_email3}}} | }}<br />
| contributor_username3 = {{#if: {{{contributor_username3|}}} | {{{contributor_username3}}} | }}<br />
| contributor_name4 = {{#if: {{{contributor_name4|}}} | {{{contributor_name4}}} | }}<br />
| contributor_email4 = {{#if: {{{contributor_email4|}}} | {{{contributor_email4}}} | }}<br />
| contributor_username4 = {{#if: {{{contributor_username4|}}} | {{{contributor_username4}}} | }}<br />
| contributor_name5 = {{#if: {{{contributor_name5|}}} | {{{contributor_name5}}} | }}<br />
| contributor_email5 = {{#if: {{{contributor_email5|}}} | {{{contributor_email5}}} | }}<br />
| contributor_username5 = {{#if: {{{contributor_username5|}}} | {{{contributor_username5}}} | }}<br />
| contributor_name6 = {{#if: {{{contributor_name6|}}} | {{{contributor_name6}}} | }}<br />
| contributor_email6 = {{#if: {{{contributor_email6|}}} | {{{contributor_email6}}} | }}<br />
| contributor_username6 = {{#if: {{{contributor_username6|}}} | {{{contributor_username6}}} | }}<br />
| contributor_name7 = {{#if: {{{contributor_name7|}}} | {{{contributor_name7}}} | }}<br />
| contributor_email7 = {{#if: {{{contributor_email7|}}} | {{{contributor_email7}}} | }}<br />
| contributor_username7 = {{#if: {{{contributor_username7|}}} | {{{contributor_username7}}} | }}<br />
| contributor_name8 = {{#if: {{{contributor_name8|}}} | {{{contributor_name8}}} | }}<br />
| contributor_email8 = {{#if: {{{contributor_email8|}}} | {{{contributor_email8}}} | }}<br />
| contributor_username8 = {{#if: {{{contributor_username8|}}} | {{{contributor_username8}}} | }}<br />
| contributor_name9 = {{#if: {{{contributor_name9|}}} | {{{contributor_name9}}} | }}<br />
| contributor_email9 = {{#if: {{{contributor_email9|}}} | {{{contributor_email9}}} | }}<br />
| contributor_username9 = {{#if: {{{contributor_username9|}}} | {{{contributor_username9}}} | }}<br />
| contributor_name10 = {{#if: {{{contributor_name10|}}} | {{{contributor_name10}}} | }}<br />
| contributor_email10 = {{#if: {{{contributor_email0|}}} | {{{contributor_email0}}} | }}<br />
| contributor_username10 = {{#if: {{{contributor_username10|}}} | {{{contributor_username10}}} | }}<br />
| pamphlet_link = {{#if: {{{pamphlet_link|}}} | {{{pamphlet_link}}} | }}<br />
| presentation_link = {{#if: {{{presentation_link|}}} | {{{presentation_link}}} | }}<br />
| mailing_list_name = {{#if: {{{mailing_list_name|}}} | {{{mailing_list_name}}} | }}<br />
| links_url1 = {{#if: {{{links_url1|}}} | {{{links_url1}}} | }}<br />
| links_name1 = {{#if: {{{links_name1|}}} | {{{links_name1}}} | }}<br />
| links_url2 = {{#if: {{{links_url2|}}} | {{{links_url2}}} | }}<br />
| links_name2 = {{#if: {{{links_name2|}}} | {{{links_name2}}} | }}<br />
| links_url3 = {{#if: {{{links_url3|}}} | {{{links_url3}}} | }}<br />
| links_name3 = {{#if: {{{links_name3|}}} | {{{links_name3}}} | }}<br />
| links_url4 = {{#if: {{{links_url4|}}} | {{{links_url4}}} | }}<br />
| links_name4 = {{#if: {{{links_name4|}}} | {{{links_name4}}} | }}<br />
| links_url5 = {{#if: {{{links_url5|}}} | {{{links_url5}}} | }}<br />
| links_name5 = {{#if: {{{links_name5|}}} | {{{links_name5}}} | }}<br />
| links_url6 = {{#if: {{{links_url6|}}} | {{{links_url6}}} | }}<br />
| links_name6 = {{#if: {{{links_name6|}}} | {{{links_name6}}} | }}<br />
| links_url7 = {{#if: {{{links_url7|}}} | {{{links_url7}}} | }}<br />
| links_name7 = {{#if: {{{links_name7|}}} | {{{links_name7}}} | }}<br />
| links_url8 = {{#if: {{{links_url8|}}} | {{{links_url8}}} | }}<br />
| links_name8 = {{#if: {{{links_name8|}}} | {{{links_name8}}} | }}<br />
| links_url9 = {{#if: {{{links_url9|}}} | {{{links_url9}}} | }}<br />
| links_name9 = {{#if: {{{links_name9|}}} | {{{links_name9}}} | }}<br />
| links_url10 = {{#if: {{{links_url0|}}} | {{{links_url0}}} | }}<br />
| links_name10 = {{#if: {{{links_name10|}}} | {{{links_name10}}} | }}<br />
| project_road_map = {{#if: {{{project_road_map|}}} | {{{project_road_map}}} | }}<br />
| project_health_status = {{#if: {{{project_health_status|}}} | {{{project_health_status}}} | }} }}<br />
| valign="top" |<br />
{{Template:Releases Summary <br />
| project_name = {{#if: {{{project_name|}}} | {{{project_name}}} | }} <br />
| project_home_page= {{#if: {{{project_home_page|}}} | {{{project_home_page}}} | }}<br />
| release_1= {{{release_1|}}}<br />
| release_2= {{{release_2|}}}<br />
| release_3= {{{release_3|}}}<br />
| release_4= {{{release_4|}}}<br />
| release_5= {{{release_5|}}}<br />
| release_6= {{{release_6|}}}<br />
| release_7= {{{release_7|}}}<br />
| release_8= {{{release_8|}}}<br />
| release_9= {{{release_9|}}}<br />
| release_10= {{{release_10|}}}<br />
}}<br />
|}</includeonly><noinclude><br />
This template displays the About page summary for an OWASP Project. This tab utilizes the [[:Template:Project Info]] and [[:Template:Releases Summary]] templates. See these respective templates for default values.<br />
<br />
=== Usage ===<br />
<pre><br />
{{Template:Project About<br />
| project_name =<br />
| project_home_page =<br />
| project_description =<br />
| project_license =<br />
| leader_name[1-10] =<br />
| leader_email[1-10] =<br />
| leader_username[1-10] = <br />
| contributor_name[1-10] = <br />
| contributor_email[1-10] = <br />
| contributor_username[1-10] = <br />
| pamphlet_link = <br />
| presentation_link = http://prezi.com/ffc3mt-f8jd6/untitled-prezi/?utm_campaign=share&utm_medium=copy<br />
| mailing_list_name = <br />
| project_road_map = <br />
| links_url[1-10] = <br />
| links_name[1-10] = <br />
| release_1 = <br />
| release_2 = <br />
| release_3 =<br />
| release_4 =<br />
}}<br />
</pre><br />
<br />
=== Example ===<br />
<pre><br />
{{Template:Project About<br />
| project_name = Example Project<br />
| project_homepage = Category: GPC Templates<br />
| project_description = an example project<br />
| project_license = Creative Commons Attribution-Share Alike 3.0<br />
| leader_username1 = Jason Li<br />
| leader_name1 = Jason Li<br />
| leader_name2 = Brad Causey<br />
| contributor_username1 = mtesauro<br />
| contributor_name1 = Matt Tesauro<br />
| presentation_link = https://www.owasp.org/images/2/23/Owasp-gpc-slides_June_2009.ppt<br />
| mailing_list_name = global-projects-committee<br />
| project_road_map = Global_Projects_Committee<br />
| links_url1 = http://www.owasp.org/index.php/Global_Projects_Committee<br />
| links_name1 = Global Projects Committee<br />
}}<br />
</pre><br />
{{Template:Project About<br />
| project_name = Example Project<br />
| project_homepage = Category: GPC Templates<br />
| project_description = an example project<br />
| project_license = Creative Commons Attribution-Share Alike 3.0<br />
| leader_username1 = Jason Li<br />
| leader_name1 = Jason Li<br />
| leader_name2 = Brad Causey<br />
| contributor_username1 = mtesauro<br />
| contributor_name1 = Matt Tesauro<br />
| presentation_link = https://www.owasp.org/images/2/23/Owasp-gpc-slides_June_2009.ppt<br />
| mailing_list_name = global-projects-committee<br />
| project_road_map = Global_Projects_Committee<br />
| links_url1 = http://www.owasp.org/index.php/Global_Projects_Committee<br />
| links_name1 = Global Projects Committee<br />
}}<br />
[[Category: GPC Templates]]</noinclude></div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=153346OWASP Hive Project2013-06-10T20:29:41Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
<br />
=What is it?=<br />
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''<br />
** ''' Cost Breakdown '''<br />
*** '''Raspberry PI Cluster''' - Cost for 10 Environment Hive 500.00 (Approx) <br />
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single OWASPi HIVE-OFF''' - Cost 50.00 - 75.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per Pi)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.element14.com/community/groups/raspberry-pi element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=153345OWASP Hive Project2013-06-10T20:29:15Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
=What is it?=<br />
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''<br />
** ''' Cost Breakdown '''<br />
*** '''Raspberry PI Cluster''' - Cost for 10 Environment Hive 500.00 (Approx) <br />
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single OWASPi HIVE-OFF''' - Cost 50.00 - 75.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per Pi)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.element14.com/community/groups/raspberry-pi element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=153344OWASP Hive Project2013-06-10T20:28:50Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
=What is it?=<br />
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''<br />
* ''' Cost Breakdown '''<br />
*** '''Raspberry PI Cluster''' - Cost for 10 Environment Hive 500.00 (Approx) <br />
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single OWASPi HIVE-OFF''' - Cost 50.00 - 75.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per Pi)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.element14.com/community/groups/raspberry-pi element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=153343OWASP Hive Project2013-06-10T20:28:31Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
=What is it?=<br />
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''<br />
<br />
* ''' Cost Breakdown '''<br />
*** '''Raspberry PI Cluster''' - Cost for 10 Environment Hive 500.00 (Approx) <br />
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single OWASPi HIVE-OFF''' - Cost 50.00 - 75.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per Pi)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.element14.com/community/groups/raspberry-pi element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnsonhttps://wiki.owasp.org/index.php?title=OWASP_Hive_Project&diff=153342OWASP Hive Project2013-06-10T20:27:31Z<p>Jason Johnson: </p>
<hr />
<div>== '''WE NEED "PI's" FOR TESTING YOU CAN DONATE SOME''' ==<br />
[[File:owaspi.png|px637]]<br />
=What is it?=<br />
''' You have to [http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy watch the presentation] '''<br />
''' Cost Breakdown '''<br />
*** '''Raspberry PI Cluster''' - Cost for 10 Environment Hive 500.00 (Approx) <br />
*** '''4gb SD Card''' - Cost 8.37 (per Pi) (can be bigger)<br />
*** '''Development of HIVE cluster wifi and power''' - Cost 300.00 (Approx)<br />
*** '''Single OWASPi HIVE-OFF''' - Cost 50.00 - 75.00 (MetalCase)<br />
*** '''WiFi Mod''' - Cost 12.00 (per Pi)<br />
*** '''Starter Kit''' - Cost 20.00 - 69.00 ( the 69$ one has GPIO pinout cables )<br />
** '''The HIVE can have 10 20 50 and 100 environment HIVE. This start-up is for 10 environment. Large chapters may like the large HIVE.<br />
** '''QUOTE from [https://www.element14.com/community/groups/raspberry-pi element14 (NEWARK)]<br />
** '''[http://prezi.com/ffc3mt-f8jd6/?utm_campaign=share&utm_medium=copy OWASPi Overview]'''<br />
<br />
{{:Projects/OWASP_Hive_Project}} <br />
[[Category:OWASP Project]]</div>Jason Johnson