Hi all, El mié, 24-06-2015 a las 16:44 +0500, Ilshat Shakirov escribió: > Hello!, > > > as far as I understood, Monitor and Trusted peers are the > different names for the same type of peer. > > > No, this is 2 different peers in the team. Is it right?
Actually, a monitor in STrPe check that everything is correct and to reduce repeated work it can acts a trusted peer. > We need to perform more realistic scenarios. For instance a > group of people sharing a video. > > > Ok. > > > Let fix the number of well intended peers to 20. > 1.1 and 1.2 seems to be solved. > 1.3 also. > What about 1.2-1.3 together. As malicious peer, once > discovered I guess who is the Trusted peer I will sent good > chunks in new off-on connection. > So I can perform a selective attack. > Does malicious 1-2-1.3 peer persists? Give an advice of how to > solve this type of attack (The code for the solution for your > advice is not part of GSoC) > 1.4 (Has no sense in STrPe) because Spliter only hear from > Trusted peer. > 1.5. DoS was not selected as one of the attacks in GSoC > 1.6. Collaborative Attack: One of the malicious peers can > inform the others about a possible Trusted peer. > > > Ok, I will edit the document to suit this conditions. > > > So, Just use a set of 20 well intended peers and add a > different number of malicious peers (1 to 40) and different > type of (basic) attacks in order to know how many malicious > peers and of what type of attacks the fix (20 well intended > peers and one Trusted peer) system can support. > System performance can be measured, for instance, in how many > good chunks have a good peer received out of all. > > > > Ok; Is there any option run peer without running a player? I'm going > to run all peers in one local machine, is it right? You can reduce the set to 10 if needed. Best, Leo
-- Mailing list: https://launchpad.net/~p2psp Post to : [email protected] Unsubscribe : https://launchpad.net/~p2psp More help : https://help.launchpad.net/ListHelp
