Diese Seite wurde zuletzt Mai 2018 aktualisiert.


Forschung über das I2P-Netzwerk

I2P ist ein einzigartiges Projekt, das von akademischer Seite leider nicht die Aufmerksamkeit erhält, die es verdient. Bis heute konzentriert sich wissenschaftliche Arbeit zu anonymen und verschachtelten Verbindungstechnologien auf das Tor-Projekt. Während diese Publikationen auch uns nützen, existiert ein großer Bedarf für Forschungsarbeiten über I2P. Dies ist der Schüssel, um sowohl die Sicherheit und Integrität des Netzwerks aufrecht zu erhalten, als auch die Tür zu noch wirkungsvolleren Entwicklungen in der Zukunft zu eröffnen.

Es existiert eine große Gruppe an Forschern, die eine große Liste an Themen zur Anonymität erforschen. Für eine aktuelle und umfassende Liste der relevanten Paper, schauen Sie in die Free Haven Anonymity Bibliography. I2P profitiert viel von der Forschung an Tor und Onion Routing, aber es gibt wenig dediziertes Interesse an der Forschung zur Theorie hinter I2P, den Entscheidungen und den Abstimmungen, die das Netzwerk macht. Dieses ist eine einzigartige Chance für originale Forschung.

Eine Liste der bekannten publizierten Paper über I2P ist hier verfügbar.

Diese Seite soll die meistbenötigten Forschungsthemen umreißen; sie enthält Hinweise an Wissenschaftler, unsere allgemeinen Sicherheitsrichtlinien sowie eine wachsende Liste offener Fragen, bei denen man ansetzen kann.

Hinweise an Wissenschaftler:


While all research on the I2P network is beneficial and appreciated, there are certain areas which are more in need than others - most so in defensive research. Most people enjoy coming up with fun ways to launch offensives against anonymous software, and this is further reinforced by the incentives in academic institutions. While we know it is often not the first choice for researchers, We would certainly appreciate any and all work towards ways to fortify the network!

Offensive und analytische Tests

If you've decided on a research topic that aims to hands-on investigate the I2P network or solve a problem of large proportions we ask you to please communicate your ideas to the development team, the sooner the better. I2P is under constant development and a significant amount of roadmapping occurs, therefore your problem may have already been identified and flagged for update or patch. In the unlikely event you are conducting testing that overlaps with / would be of interest to another research project already in motion, we are also able to make you aware of this (with their permission, of course), and possibly open the door for collaboration. There is also a chance that the test itself may significantly harm the network or regular users, and the team may have ideas or suggestions to mitigate that risk and increase the safety of your testing.

Forscherethik & Untersuchungen im Netzwerk

Allgemeine Richtlinien

  1. Consider the benefits and risks - is there any doubt that the research provides more value than danger?
  2. If the research can be done on a test network then that is the preferred method
  3. If you must operate on the live network, the safest route is only collecting data about yourself
  4. If you need 'bigger data', It is recommended to first see if you can use data sets from previous experiments or other third party resources is recommended
  5. If you must collect data on the live network, ensure it is safe for publication and collect as little as possible
  6. After testing and before publish, review that all data which is to be published publicly is not intended to be private by the originator

Using a Test Network to Attack I2P

I2P can be run as a separate test network by controlling the locations that a new router reseeds from so that it only finds other test routers. The standard mode of operation is to have one JVM per router instance; hence running multiple copies of I2P on a single machine is inadvisable, both due to the potential resource drain and the certain port conflicts. To better facilitate setting up small test networks, I2P has a multirouter mode which enables multiple distinct routers to be run in the same JVM. MultiRouter can be started from the i2p base directory by running the below command.

env CLASSPATH=$(find lib/ -name *.jar | paste -s -d ':') java net.i2p.router.MultiRouter 25

Additionally, I2P can be started in a virtual network mode. This mode disables all transports, allowing the router to be tested in isolation without network traffic. To enable this mode, add i2p.vmCommSystem=true to the router.config before starting.

Am Live I2P Netzwerk test

As stated above in the researcher notes, please contact us before you commence your testing. While we do not discourage researchers from responsibly testing their ideas on the live network, if an attack becomes apparent and we don't have any line of communication then we will end up taking countermeasures which could interfere with the test.


As of release 0.9.25, I2P supports a router family configuration. This provides researchers who run multiple routers with the means to publicly identify those routers. In turn, this helps the I2P project understand that these routers are not running an attack on the network. It also will prevent other routers from including multiple routers of the family in a single tunnel, which could lead to deanonymization. Routers that appear to be colluding but do not have a declared family may be assumed to be an attack on the network, and may be blocked. The best way to ensure the success of your research project is to work with us directly.

A router family shares a private key so that participation in the family cannot be spoofed. To configure a router family, click on the 'I2P Internals' link in the router console, and then on the 'Family' tab. Follow the instructions there to generate the private key for the first router in the family. Then, export the key from that router, and import it to other members of the family.