[www] 01/03: - added developer page

[gnunet]

This is an automated email from the git hooks/post-receive script.

t3sserakt pushed a commit to branch stable
in repository www.

commit b3b8a408ad213e1a1466926a9e055e2e3caf8800
Author: t3sserakt <t3ss@posteo.de>
AuthorDate: Sat Dec 3 12:30:36 2022 +0100

    - added developer page
---
 static/images/t3sserakt.jpg          | Bin 0 -> 11878 bytes
 template/dev_pages/t3sserakt.html.j2 | 136 +++++++++++++++++++++++++++++++++++
 2 files changed, 136 insertions(+)

diff --git a/static/images/t3sserakt.jpg b/static/images/t3sserakt.jpg
new file mode 100644
index 00000000..e4782e6a
Binary files /dev/null and b/static/images/t3sserakt.jpg differ
diff --git a/template/dev_pages/t3sserakt.html.j2 
b/template/dev_pages/t3sserakt.html.j2
new file mode 100644
index 00000000..73647b9a
--- /dev/null
+++ b/template/dev_pages/t3sserakt.html.j2
@@ -0,0 +1,136 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<!-- Jumbotron -->
+<div>
+  <div class="container">
+    <div class="row">
+      <div class="container text-center">
+        <h1>{{ _("Developer page: t3sserakt") }}</h1>
+      </div>
+    </div>
+
+    <div class="container text-center">
+      <img src="{{ url_static('images/t3sserakt.jpg') }}"  alt="t3sserakt" />
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+        <section>
+        <h2>{{ _("Current Work") }}</h2>
+        <p>
+        {% trans %}
+          At the moment I am working on Transport Next Generation (TNG). The 
current GNUnet TRANSPORT architecture with its pluggable transport mechanism 
(TCP, UDP, HTTP(S) and other protocols) together with the ATS subsystem for 
bandwidth allocation and choosing plugins has several issues with its design. 
With the Layer-2-Overlay project we like to implement the design goals of the 
future GNUnet TRANSPORT Next Generation (TNG) subsystem. For details have a 
look on the <a href="https://w [...]
+      {% endtrans %}
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+      <section>
+        <h2>{{ _("Future Work") }}</h2>
+        <p>
+          {% trans %}
+            The next project I will work on is named "Probabilistic NAT 
Traversal".
+          {% endtrans %}
+        </p>
+       <p>
+         {% trans %}
+            Today consumer devices are behind a NAT quite often, restricting 
internet connectivity. There are several methods to reach peers being
+behind a NAT, but there are as many reasons those existing methods might fail. 
We will implement a new way of NAT traversal that we
+think of being independent from the existing network configuration, and does 
not require a third party which is not natted helping two
+peers to connect to each other. Two peers trying to connect to each other will 
send out a burst of connection attempts to the other peer on
+different ports. The sheer vast amount of connections attempts from both side 
will lead to a high probability that two connection attempts
+from both peers onto the same port will be at the same time leading to a 
successful connection between those peers.
+         {% endtrans %}
+       </p>
+        <p>
+          {% trans %}
+            There are two problems a NAT traversal method has to solve. First 
there needs to be a method to know the global IP address of a peer A
+another peer B wants to connect to. Second – because inbound connections from 
the outside are blocked by the NAT firewall of peer A,
+peer A needs to be informed of a connection attempt by peer B. The most common 
solution for both problems is to have a third party C
+which is not behind a NAT. This third party C obviously knows the global IP 
address of natted peers, after peer A is trying to connect to
+C. Peer B tells C it likes to connect to peer A, and C informs A about it. 
Using this method for a privacy preserving network like GNUnet,
+this could facilitate eclipse attacks (isolating a peer) which then can be 
used for deanonymization attacks and cencorship. Also any
+additional infrastructure needed to provide some kind of functionality has to 
be maintained by someone, becoming a target and/or point of
+failure. Therefore this method is not suitable. More sophisticated methods 
like "Autonomous NAT Traversal (pwnat)" using ICMP fake
+message, which do not need a third party for the initiation of the connection, 
are not successful in all circumstances, because this method
+depend on the behavior of the NAT firewall.
+          {% endtrans %}
+        </p>
+       <p>
+          {% trans %}
+            If two natted peers are using the method to start a burst of 
connection attempts, this method still needs the global IP of the other peer 
and a “start signal” to coordinate. In the NGI Assure project L2O we are 
establishing a backchannel with neighbourhood routing over an ad-
+hoc distance vector protocol to solve the problem of not directly connected 
peers. The peers serving as hops to a distant peer which are a
+direct neighbour of the start or end peer on that path do know the global IP 
address of the start or end peer. If those two peers like to use
+the burst method for hole punching the global IP address is known. Via the 
distance vector protocol we are also able to communicate the
+"start signal". Also in the L2O project we introduced a new test framework for 
GNUnet to test network setups with peers having
+restricted connectivity. This test framework will be used to create test 
setups suitable to test possible NAT configurations. A challenge for
+this NAT traversal method will be how to handle the burst in terms of network 
load, thus we need to experiment with different
+frequencies and the amount of connection attempts.
+          {% endtrans %}
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+      <section>
+        <h2>{{ _("Past Work") }}</h2>
+        <p>
+          {% trans %}
+            In the past I have tried to help making the vision of the <a 
href="http://secushare.org";>secushare</a> project a reality. To achieve this 
the GNUnet framework was the perfect match for a solution to fullfill the 
privacy preserving part of that vision, and we could concentrate to build a 
tool for social communication that deserves its name. While trying to use 
GNUnet, we found and fixed bugs. For example there was one <a 
href="https://bugs.gnunet.org/view.php?id=5822";>bug</a>  [...]
+          {% endtrans %}
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+      <section>
+        <h2>{{ _("Contact Information") }}</h2>
+        <p>
+         <div class="container">
+           <div class="row">
+             <div class="col-lg-2">Mail:</div>
+             <div class="col-lg-6">t3sserakt@gnunet.org</div>
+           </div>
+           <div class="row">
+             <div class="col-lg-2">Mastodon:</div>
+             <div class="col-lg-6">@t3sserakt@social.tchncs.de</div>
+           </div>
+           <div class="row">
+             <div class="col-lg-2">Matrix:</div>
+             <div class="col-lg-6">@t3sserakt:tchncs.de</div>
+           </div>
+           <div class="row">
+             <div class="col-lg-2">PGP:</div>
+             <div class="col-lg-6"><a 
href="https://keyoxide.org/hkp/34156165BAC792A688C990CFC9A2D9D808FF308D";>keyoxide</a></div>
+           </div>
+         </div>
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+{% endblock body_content %}

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.