How to Automate Sharing Cryptographic Keys With Other OneSwarm Users

The oneSwarm protocol uses cryptographic keys to identify each OneSwarm user among its peers. OneSwarm identities are persistent and can be accessed when online, whereas IP-addresses and port numbers are transient. OneSwarm users are also linked to a distributed hash table, which stores all user information. Users can automate the process of sharing their cryptographic keys with one another using three methods. The first method is a browser plugin, which allows users to share parts of their files with other OneSwarm users.

Another method for defeating this attack is to introduce a random response delay. This delay should be consistent for a particular file, but long enough so that the attacker cannot identify the difference between the response time from one peer and that of another. OneSwarm implements this technique by adding a 150 to 300-millisecond delay before answering a query. This makes it difficult for attackers to determine whether the difference is due to network jitter or a forwarded query.

Another method for increasing the speed of OneSwarm is dynamically assigning peers. This technique improves contributions by limiting attackers from injecting their own nodes. OneSwarm also makes link types private so that it is impossible for others to guess whether a certain link is trusted or untrusted. This method makes it harder for attackers to infiltrate the OneSwarm network, which enables OneSwarm to increase speed and reduce costs.