Do i need a user registration to work with the DHT? see #7
Do i need a file / data signature to identify data manipulation from a malicious third party?
I need a trackerless p2p-network to be more resilient and no need for separate server infrastructure.
In the bittorrent network with dht, it is not natively possible to update / add / remove files or arbitrary data. But there are already BEPs for this use cases.
The user should use their smartphones and laptops with mobile internet to work with this application, so i need a resilient way to work with disconnects. But in first place, the data should be transfered, if the mobile device has a wlan connection.
To make the dht more resilient against devices, which are disconnect (because the user closed the application), it is needed, that there are replicants to reduce the possibility to find no seeder.
There is a possibility from attackers, which try to get into the swarm and get informations. The publisher itself is a node, so he can be a private tracker which replicates himself on another device (example: laptop replicate himself on smartphone, if it is set as a replication-device with sufficient permissions and the public key was set into the settings).
Do i need a user registration to work with the DHT? see #7 Do i need a file / data signature to identify data manipulation from a malicious third party?
I need a trackerless p2p-network to be more resilient and no need for separate server infrastructure.
In the bittorrent network with dht, it is not natively possible to update / add / remove files or arbitrary data. But there are already BEPs for this use cases.
It is needed to sign the torrents with private key, so the user can be safer about the given data.
The user should use their smartphones and laptops with mobile internet to work with this application, so i need a resilient way to work with disconnects. But in first place, the data should be transfered, if the mobile device has a wlan connection.
To make the dht more resilient against devices, which are disconnect (because the user closed the application), it is needed, that there are replicants to reduce the possibility to find no seeder.
Security extension against standard attacks
Extend protocol
There is a possibility from attackers, which try to get into the swarm and get informations. The publisher itself is a node, so he can be a private tracker which replicates himself on another device (example: laptop replicate himself on smartphone, if it is set as a replication-device with sufficient permissions and the public key was set into the settings).