netdev - [RFC] new connection-oriented layer 3+4 protocol

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20120919170853.GJ2228@grml>
Date:	Wed, 19 Sep 2012 19:08:53 +0200
From:	michi1@...haelblizek.twilightparadox.com
To:	netdev@...r.kernel.org, davem@...emloft.net
Subject: [RFC] new connection-oriented layer 3+4 protocol

Hi!

I am programming a new layer 3+4 protocol for mesh networks. Basically it is
- connection oriented
- source (+optional onion) routed
- doing windowing between each neighbor on every connection (no congestion
  avoidance)
- using credits as a metric for QoS

The protocol especially tries to withstand DoS attacks and rough
users/application without human interference. This includes protection against
inserting bogus routes, blackholing/throttling, addressing conflicts (node
address can be a hashed public crypto key) and ressource contention. In theory
it could provide Byzantine robustness, but in practice the overhead for
calculating routes and ressource contention will limit how far this gets.

Right now the layer 3 is running somehow (without any crypto). The layer 4 is
currently rather incomplete and broken.

Project home:
http://michaelblizek.homelinux.net/projects/cor/index.html

Code:
http://repo.or.cz/w/cor.git/tree/HEAD:/net/cor

        -Michi
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html