OWASP Hive Project
WELCOME TO THE GRID
gggrgM**M#mggg__ __wgNN@"B*P""mp""@d#"@N#Nw__ _g#@0F_a*F# _*F9m_ ,F9*__9NG#g_ _mN#F aM" #p" !q@ 9NL "9#Qu_ g#MF _pP"L _g@"9L_ _g""#__ g"9w_ 0N#p _0F jL*" 7_wF #_gF 9gjF "bJ 9h_ j# gAF _@NL WELCOME J@u_ 2#_ #_ ,FF_#" 9_ _#" "b_ g@ "hg _#" !q_ jF "*_09_ F N" #p" Ng@ TO `#g" "w@ "# t j p# g"9_ g@"9_ gP"#_ gF"q Pb L 0J k _@ 9g_ j#" "b_ j#" "b_ _d" q_ g ## #F `NF "#g" THE "Md" GRID 5N# 9W" j# #k jFb_ g@"q_ _*"9m_ _*"R_ _#Np J# tApjF 9g J" 9M_ _m" 9%_ _*" "# gF 9_jNF k`N "q# 9g@ #gF ##" #"j `_0q_ #"q_ _&"9p_ _g"`L_ _*"# jAF,' 9# "b_j "b_ g" *g _gF 9_ g#" "L_*"qNF "b_ "#_ "NL _B# _I@ j#" _#" NM_0"*g_ j""9u_ gP q_ _w@ ]_ _g*"F_g@ "NNh_ !w#_ 9#g" "m*" _#*" _dN@" 9##g_0@q__ #"4_ j*"k __*NF_g#@P" "9NN#gIPNL_ "b@" _2M"Lg#N@F" ""P@*NN#gEZgNN@#@P""
Temp introducer URL
What is it?
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
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/
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.
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.
The milestones that I anticipate are:
Sweet user interface Find a LCD for the BeagleBone Black for IP or stats scrolling. The HIVE setup currently shows the nodes in real time. (expand more on this) Make a proposal to OWASP for a more stable introducer and private GRID.
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What releases are available for this project?