commits August 2024

commits@lists.open-mesh.org

1 participants
41 discussions

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (41e38975)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 41e389756fb063bf1ce997a9d3dd19f669542c58 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 12:02:15 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- 41e389756fb063bf1ce997a9d3dd19f669542c58 open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index 539a38b9..49030f1b 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -13,7 +13,7 @@ In a wireless community mesh network like "Freifunk":https://en.wikipedia.org/wi # Anyone can setup a node to join + contribute to the mesh # No prior authorization, anonymous participation possible -has two issues: +Currently has the following two issues: # A user's internet traffic is typically unencrypted in the WLAN mesh cloud (except for https etc.) # A set of central gateways behind a VPN tunnel is used for internet traffic (which contradicts Freifunk's philosophy of decentralization, but became defacto mandatory due to for private people unclear Secondary Liability law in Germany: "''Störerhaftung''":https://de.wikipedia.org/wiki/St%C3%B6rerhaftung)

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (5a8662f8)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 5a8662f829903bd6ec8ce45d043f6e49167b41a7 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 12:03:57 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- 5a8662f829903bd6ec8ce45d043f6e49167b41a7 open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index 27470545..29c60a6a 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -11,8 +11,8 @@ h3. A) - Issues in Decentral Wireless Community Mesh Networks In a wireless community mesh network like "Freifunk":https://en.wikipedia.org/wiki/Freifunk involving "batman-adv":https://www.open-mesh.org/projects/batman-adv/wiki/ + "Gluon":https://github.com/freifunk-gluon/gluon/: # Anyone can setup a node to join + contribute to the mesh -# OpenSource firmware code # No prior authorization, anonymous participation possible +# Uses OpenSource firmware code Currently has the following two issues:

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (ef79c3c0)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit ef79c3c0d9f6fdac36d53b78fe05c89748605c2f Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 12:01:36 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- ef79c3c0d9f6fdac36d53b78fe05c89748605c2f open-mesh/OpenHarbors.textile | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index f8afcceb..539a38b9 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -8,7 +8,12 @@ h2. Issues h3. A) - Issues in Decentral Wireless Community Mesh Networks -In a wireless community mesh network like "Freifunk":https://en.wikipedia.org/wiki/Freifunk involving "batman-adv":https://www.open-mesh.org/projects/batman-adv/wiki/ + "Gluon":https://github.com/freifunk-gluon/gluon/ has two issues: +In a wireless community mesh network like "Freifunk":https://en.wikipedia.org/wiki/Freifunk involving "batman-adv":https://www.open-mesh.org/projects/batman-adv/wiki/ + "Gluon":https://github.com/freifunk-gluon/gluon/: + +# Anyone can setup a node to join + contribute to the mesh +# No prior authorization, anonymous participation possible + +has two issues: # A user's internet traffic is typically unencrypted in the WLAN mesh cloud (except for https etc.) # A set of central gateways behind a VPN tunnel is used for internet traffic (which contradicts Freifunk's philosophy of decentralization, but became defacto mandatory due to for private people unclear Secondary Liability law in Germany: "''Störerhaftung''":https://de.wikipedia.org/wiki/St%C3%B6rerhaftung)

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (750371d4)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 750371d4a03b3396cc88b8bcce23d061306ee9f7 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 11:57:17 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- 750371d4a03b3396cc88b8bcce23d061306ee9f7 open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index 79cb85a9..d35a66db 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -21,7 +21,7 @@ Gluon also supports adding the following three types of WLAN encryption: # "OWE":https://en.wikipedia.org/wiki/Opportunistic_Wireless_Encryption to encrypt traffic from a user device to the direct mesh node / AP: "OWE on client network":https://gluon.readthedocs.io/en/latest/releases/v2020.2.html#owe-on-client-network # A "''Private WiFi''":https://gluon.readthedocs.io/en/latest/features/private-wlan.html with WPA-Personal/preshared key encryption, simply bridged to a mesh node's WAN port -While 1)+2) protects against passive snooping, it however **does not protect against an active attacker** in an open, public network like Freifunk. Due to the open nature of Freifunk, the SAE password would need to be published / added to the firmware (source code) to allow anyone to setup their own mesh node. So overall Freifunk even with 1)+2) would still be susceptible to Man-in-the-Middle attacks. +While 1)+2) protects against passive snooping, it however **does not protect against an active attacker in an open, public network** like Freifunk. Due to the open nature of Freifunk, the SAE password would need to be published / added to the firmware (source code) to allow anyone to setup their own mesh node. So overall Freifunk even with 1)+2) would still be susceptible to Man-in-the-Middle attacks. The issue with option 3) is that while it is secure, as the mesh node owner can configure their own, private password for it in the Gluon Config-Mode Web-GUI of their Gluon mesh router, it can't be used on foreign, other mesh nodes over the mesh network. There is no secure tunneling or provisioning/collaboration between mesh nodes for the "Private WiFi" feature in Gluon.

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (42683fcf)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 42683fcf3cf786fa5ca9555505b6a1827cd8a49c Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 11:58:20 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- 42683fcf3cf786fa5ca9555505b6a1827cd8a49c open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index d35a66db..f8afcceb 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -21,7 +21,7 @@ Gluon also supports adding the following three types of WLAN encryption: # "OWE":https://en.wikipedia.org/wiki/Opportunistic_Wireless_Encryption to encrypt traffic from a user device to the direct mesh node / AP: "OWE on client network":https://gluon.readthedocs.io/en/latest/releases/v2020.2.html#owe-on-client-network # A "''Private WiFi''":https://gluon.readthedocs.io/en/latest/features/private-wlan.html with WPA-Personal/preshared key encryption, simply bridged to a mesh node's WAN port -While 1)+2) protects against passive snooping, it however **does not protect against an active attacker in an open, public network** like Freifunk. Due to the open nature of Freifunk, the SAE password would need to be published / added to the firmware (source code) to allow anyone to setup their own mesh node. So overall Freifunk even with 1)+2) would still be susceptible to Man-in-the-Middle attacks. +While 1)+2) protects against passive snooping, it however **does not protect against an active attacker in an open, public network** like Freifunk. Due to the open nature of Freifunk, the **SAE password would need to be published** / added to the firmware (source code) to allow anyone to setup their own mesh node. So overall Freifunk even with 1)+2) would still be susceptible to Man-in-the-Middle attacks. The issue with option 3) is that while it is secure, as the mesh node owner can configure their own, private password for it in the Gluon Config-Mode Web-GUI of their Gluon mesh router, it can't be used on foreign, other mesh nodes over the mesh network. There is no secure tunneling or provisioning/collaboration between mesh nodes for the "Private WiFi" feature in Gluon.

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (7cf1a46c)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 7cf1a46c50460a1c9a746b3e8f72d8d3a8c6b5b4 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 11:56:44 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- 7cf1a46c50460a1c9a746b3e8f72d8d3a8c6b5b4 open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index e5716a74..79cb85a9 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -21,7 +21,7 @@ Gluon also supports adding the following three types of WLAN encryption: # "OWE":https://en.wikipedia.org/wiki/Opportunistic_Wireless_Encryption to encrypt traffic from a user device to the direct mesh node / AP: "OWE on client network":https://gluon.readthedocs.io/en/latest/releases/v2020.2.html#owe-on-client-network # A "''Private WiFi''":https://gluon.readthedocs.io/en/latest/features/private-wlan.html with WPA-Personal/preshared key encryption, simply bridged to a mesh node's WAN port -While 1)+2) protects against passive snooping, it however does not protect against an active attacker in an open, public network like Freifunk. Due to the open nature of Freifunk, the SAE password would need to be published / added to the firmware (source code) to allow anyone to setup their own mesh node. So overall Freifunk even with 1)+2) would still be susceptible to Man-in-the-Middle attacks. +While 1)+2) protects against passive snooping, it however **does not protect against an active attacker** in an open, public network like Freifunk. Due to the open nature of Freifunk, the SAE password would need to be published / added to the firmware (source code) to allow anyone to setup their own mesh node. So overall Freifunk even with 1)+2) would still be susceptible to Man-in-the-Middle attacks. The issue with option 3) is that while it is secure, as the mesh node owner can configure their own, private password for it in the Gluon Config-Mode Web-GUI of their Gluon mesh router, it can't be used on foreign, other mesh nodes over the mesh network. There is no secure tunneling or provisioning/collaboration between mesh nodes for the "Private WiFi" feature in Gluon.

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (b9d41c5c)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit b9d41c5cee8370a28f6a4df431e75a91382a565b Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 11:54:16 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- b9d41c5cee8370a28f6a4df431e75a91382a565b open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index f4fd34ab..a08ed06d 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -6,7 +6,7 @@ This document specifies a way to dynamically tunnel WPA over a potentially untru h2. Issues -h3. A) - Decentral Wireless Community Mesh Networks +h3. A) - Issues in Decentral Wireless Community Mesh Networks In a wireless community mesh network like "Freifunk":https://en.wikipedia.org/wiki/Freifunk involving "batman-adv":https://www.open-mesh.org/projects/batman-adv/wiki/ + "Gluon":https://github.com/freifunk-gluon/gluon/ has two issues:

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (33d63d40)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 33d63d4010a5f024d3b26ce8c222812f60b34446 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 11:54:04 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- 33d63d4010a5f024d3b26ce8c222812f60b34446 open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index 61157bc2..f4fd34ab 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -6,7 +6,7 @@ This document specifies a way to dynamically tunnel WPA over a potentially untru h2. Issues -h3. Scenario A) - Decentral Wireless Community Mesh Networks +h3. A) - Decentral Wireless Community Mesh Networks In a wireless community mesh network like "Freifunk":https://en.wikipedia.org/wiki/Freifunk involving "batman-adv":https://www.open-mesh.org/projects/batman-adv/wiki/ + "Gluon":https://github.com/freifunk-gluon/gluon/ has two issues:

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (2ab9fc7b)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 2ab9fc7b72f8f93808c8fa2548440bffb30916ae Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 11:54:42 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- 2ab9fc7b72f8f93808c8fa2548440bffb30916ae open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index a08ed06d..e5716a74 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -27,7 +27,7 @@ The issue with option 3) is that while it is secure, as the mesh node owner can !OpenHarbors-diagram-freifunk.png! -h3. Issues with Passpoint/Hotspot 2.0/OpenRoaming solutions +h3. A) Issues with Passpoint/Hotspot 2.0/OpenRoaming solutions Industry leaders currently seem to propose and advocate for solutions based on "Passpoint/Hotspot 2.0":https://en.wikipedia.org/wiki/Wi-Fi_hotspot#Hotspot_2.0 (which in turn utilizes/builds upon "WPA-Enterprise":https://en.wikipedia.org/wiki/Wi-Fi_Protected_Access#Target_users_(authentication_key_distribution)). Potentially with "WBA OpenRoaming":https://wballiance.com/openroaming/ (Informational RFC: "here":https://datatracker.ietf.org/doc/draft-tomas-openroaming/ or similar trust/contract relations as a federation. Hotspot 2.0 was/is also a requirement for the EU "WiFi4EU":https://wifi4eu.ec.europa.eu/#/home initiative/funding.

1 0

[doc] backup-redmine,main: doc: open-mesh/OpenHarbors (e93e65a1)
by postmaster＠open-mesh.org 03 Aug '24

03 Aug '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit e93e65a19814505bbdd5209a1caed3f3cc7833ad Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Jul 8 11:53:51 2024 +0000 doc: open-mesh/OpenHarbors >--------------------------------------------------------------- e93e65a19814505bbdd5209a1caed3f3cc7833ad open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index 075ec021..61157bc2 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -6,7 +6,7 @@ This document specifies a way to dynamically tunnel WPA over a potentially untru h2. Issues -h3. Scenario A) - Issues in Decentral Wireless Community Mesh Networks +h3. Scenario A) - Decentral Wireless Community Mesh Networks In a wireless community mesh network like "Freifunk":https://en.wikipedia.org/wiki/Freifunk involving "batman-adv":https://www.open-mesh.org/projects/batman-adv/wiki/ + "Gluon":https://github.com/freifunk-gluon/gluon/ has two issues:

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits August 2024