Echt Dezentrales Netz/ TestInfrastructure: Unterschied zwischen den Versionen

Aus C3D2
Zur Navigation springen Zur Suche springen
Keine Bearbeitungszusammenfassung
Zeile 46: Zeile 46:
# '''Pentesting''' (anonymity, encryption, ...see [https://wiki.c3d2.de/Echt_Dezentrales_Netz/AttackScenarios attack scenarios])
# '''Pentesting''' (anonymity, encryption, ...see [https://wiki.c3d2.de/Echt_Dezentrales_Netz/AttackScenarios attack scenarios])
# '''Usability''' of the Gui(s)
# '''Usability''' of the Gui(s)
# Proving that the implementation covers the formal specifications
# Testing of all components (unit test)
# Testing of the overall system (audit)

Version vom 21. Februar 2015, 23:05 Uhr

Hardware

  1. Which hardware do we want to integrate? (Routers, Rasberri Pis, Smartphones, Laptops, Redlight transmitter, self built antennas, ukw sender/receiver, satellite uplink, Wifi enabled TVs also known as "Smart"TVs, [?])
  2. Which extra hardware is required? (wether resistant cases, cables, adapter, power supply)
    • What are the costs for the required parts?
    • For which hardware do we want to test EDN?

that has been found so far:

  • openwrt supported Open Hardware Router: Linksys WRT54G, 4MB Flash, 16MB RAM, akutell Neukauf: 42€
    • openwrt supported Raspberry Pis sind A,B (Ethernet 10/100) und B+ (ca. 30€ + 10€ Hülle) mit 256-512 MB RAM,CPU 700Mhz keinen Flashspeicher, Raspberry Pi 2 ist noch nicht bekannt, ob openwrt-fähig, bietet mehr Leistung zu gleichem Preis. 900MHz quad-core ARM Cortex-A7 CPU supported by 1GB LPDDR2 SDRAM
    • Banana Pi Board 1GB RAM, Gigabit Ethernet, ARMv7 Processor, 40€ ohne Extras wie Hülle, Stromversorgungskabel, externer Datenträger

Software

  1. Which OSs and Systems do we want to put on the hardware?
    • open-wrt, dd-wrt, tomato, CyanogenMod, Replicant, Debian, Gluon(openwrt-based Freifunk Firmware)
    • CJDNS, GNUnet, BALL, ....(or sequential testing according to the project's status ?)
  2. How many nodes do we want to install at least to have a realistic test field?
  3. What exactly do we want to test?
  4. Which Tools could be useful for testing?
    • Luci (web interface)
    • Aircrack ("In fact, Aircrack-ng is a set of tools for auditing wireless networks.")
    • Json
    • ?
  5. Where do we want to test?
  6. How to manage the test infrastructure?(updating, setting parameters)
    • Under which criteria do we put the management of the testing infrastructure?


What does BattleMesh already test by which means?


Testing Objectives

Which of these criteria are measurable?

  1. Performance
    • Several Routing protocols for messaging.
    • ... for telephone
  2. ?
  3. Pentesting (anonymity, encryption, ...see attack scenarios)
  4. Usability of the Gui(s)
  5. Proving that the implementation covers the formal specifications
  6. Testing of all components (unit test)
  7. Testing of the overall system (audit)