diff options
author | bnewbold <bnewbold@robocracy.org> | 2012-07-19 23:00:07 -0400 |
---|---|---|
committer | bnewbold <bnewbold@robocracy.org> | 2012-07-19 23:00:07 -0400 |
commit | 119827fd4567cd51f450dda37c3ef9600ed62979 (patch) | |
tree | d2105e4bdc21f77faa2f10879268a31d3124eba5 | |
parent | 37d7e79cfc4bfd1617de7423c73ff3cd43ee20d6 (diff) | |
download | rooter_wiki-119827fd4567cd51f450dda37c3ef9600ed62979.tar.gz rooter_wiki-119827fd4567cd51f450dda37c3ef9600ed62979.zip |
backup
-rw-r--r-- | dreamplug.page | 8 | ||||
-rw-r--r-- | mesh.page | 6 | ||||
-rw-r--r-- | security.page | 8 | ||||
-rw-r--r-- | unsorted.page | 16 |
4 files changed, 38 insertions, 0 deletions
diff --git a/dreamplug.page b/dreamplug.page index f8c26eb..e15f167 100644 --- a/dreamplug.page +++ b/dreamplug.page @@ -19,6 +19,14 @@ http://blog.bertelsen.co/2011/06/setting-up-guruplug-as-router-with.html http://plugcomputer.org/plugwiki/index.php/Setting_GuruPlug_to_be_a_WiFi_Access_Point +See James' email: + + Date: Sat, 16 Jun 2012 12:06:27 -0400 + From: James Valleroy <james.valleroy@gmail.com> + To: freedombox-discuss@lists.alioth.debian.org + Subject: [Freedombox-discuss] WiFi + + OpenWRT Experimentation ========================== diff --git a/mesh.page b/mesh.page new file mode 100644 index 0000000..3c3c7ba --- /dev/null +++ b/mesh.page @@ -0,0 +1,6 @@ + +BattleMesh is a mesh networking interop/competition, where developers of +multiple mesh protocols and stacks (babel, batman, olsr, etc) show up and test +using OpenWRT on standard hardware. + +http://battlemesh.org/BattleMeshV5 diff --git a/security.page b/security.page index dea8a2e..81bed52 100644 --- a/security.page +++ b/security.page @@ -13,3 +13,11 @@ XSS attack to back out geo location of router: <http://samy.pl/mapxss/> [Tripphrases](http://worrydream.com/tripphrase/) plan9 security: [Factotum](http://doc.cat-v.org/plan_9/4th_edition/papers/auth) + +Users should probably have a single "root" GPG key for every distinct +identity/persona that they present to the external world, and then generate +subkeys for use with each host/device and external service. This allows more +fine grained control over revokation and access control (eg, if a device is +lost then suspend/revoke that key). An API or tools to help distribute +certificates, signing information, and revokations would be helpful. + diff --git a/unsorted.page b/unsorted.page index 7c4b9a6..1938bf7 100644 --- a/unsorted.page +++ b/unsorted.page @@ -86,6 +86,10 @@ atheros stuff: # Writings, Documents +EFF Open Wireless Movement: +https://www.eff.org/deeplinks/2011/04/open-wireless-movement/ +http://www.schneier.com/blog/archives/2008/01/my_open_wireles.html + telekommunist writings: <http://www.dmytri.info/privacy-moglen-ioerror-rp12/> @@ -190,3 +194,15 @@ lightweight linux virtual machining: WiFi Direct (device-to-device) [MQTT light pubsub protocol](http://en.wikipedia.org/wiki/MQ_Telemetry_Transport) + +Securing Linux LXC containers: +http://www.ibm.com/developerworks/linux/library/l-lxc-security/ + +wi-viz: wifi network visualizations +http://devices.natetrue.com/wiviz/ + +python library for analyzing graphs/networks (w/ raster+HTML visualization?): +http://networkx.lanl.gov/ + +quantifying unsavory p2p network usage: +http://arxiv.org/abs/1206.4166 |