|author||psyc://loupsycedyglgamf.onion/~lynX <ircs://psyced.org/youbroketheinternet>||2019-03-21 19:29:40 +0000|
|committer||psyc://loupsycedyglgamf.onion/~lynX <ircs://psyced.org/youbroketheinternet>||2019-03-21 19:29:40 +0000|
gsoc/vpn: less technical description
1 files changed, 2 insertions, 16 deletions
diff --git a/news/2019-02.inc b/news/2019-02.inc
index 6c338528..63fb572b 100644
@@ -108,18 +108,7 @@ Mentor: Martin Schanzenbach
<h4>Enable all networking applications to run over GNUnet out of the box</h4>
-For many kinds of applications we need to authenticate incoming
-connections as coming from a certain person or at least from a
-The GNUnet exit daemon is currently not providing a way to
-find out who is calling.
-Resolving the virtual IP number would be the most backward
-compatible method. Best if it resolves to the same "hostname"
-as the matching outgoing <nickname>.gnu, or even uses the
-same virtual IP as an outgoing VPN tunnel would use.
-We have discussed about this topic at the 2018 GNUnet Hacker
-Meeting, and concluded that this will take
+One great problem of the current Internet is the lack of disintermediation. When people want to talk they need a chat service. When they want to share files they need a file transfer service. Although GNUnet already possesses quite advanced integration into Linux networking, a little extra work is needed for existing applications like irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. Once people have added a person to their GNS they can immediately message, exchange files and suchlike directly, with nothing but the GNUnet in the middle, using applications that have been distributed with unix systems ever since the 1980's. We can produce an OS distribution where these things work out of the box with the nicknames of people instead of cloud services. We have discussed about this topic at the 2018 GNUnet Hacker Meeting, and concluded that this will take
<li>deterministic allocation of IP addresses in exit range by PeerId AND CADET port.</li>
@@ -127,13 +116,10 @@ Meeting, and concluded that this will take
<li>new service that hijacks DNS reverse lookups in the exit range, mapping them to its own GNS zone where labels are mapped to VPN records with the information from (2), and the label.zone is returned for the reverse lookup.</li>
-If we implement this, all networking applications will be able to use
-GNUnet out of the box. Instead of implementing gnunet-native solutions
-over and over again, existing ones can be reused.<br>
For more information and context, read <a href="https://bugs.gnunet.org/view.php?id=4625">bug id 4625</a>.