Ludovic Courtès wrote: > Hello! > > Loic Dachary <l...@dachary.org> writes: > > >> The context in which I am exploring this topic is a collaborative search >> software ( http://seeks-project.info/ ). >> > > Heh, good to learn. ;-) > > Indeed, I think there are application-specific security concerns, e.g., > search keyword poisoning: a malicious party could attempt to pollute the > search results for given keyword. > > GNUnet’s anonymous file sharing encoding/protocol (ECRS) prevents users > from replying random data to keyword searches [0]. I think it can’t > directly prevent users from inserting arbitrary content under popular > keywords, though, but the fact that content replication is partly > demand-driven may mitigate it. > > It looks like compromise is in order, indeed.
The key question, it seems, is :
* given the most frequent use cases of the collaborative search software
* given the known security issues that threaten any DHT + those
specific to the application
* given the existing counter measures (ECRS among others)
=> is it likely that users will be able to effectively use the software
or will they be disrupted
by security problems at a frequency that will be discouraging for
most ?
Maybe it is a naïve way to approach the problem. I'm struggling to find
a way to understand this topic and your help is much appreciated :-)
> YaCy may also address some of the concerns you may have [1].
>
I did not see anything related to resolving security issues in YaCy, but
it was my first exploration and I may have missed the relevant part. Did
you think of something specific ?
Cheers
<<attachment: loic.vcf>>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ p2p-hackers mailing list p2p-hackers@lists.zooko.com http://lists.zooko.com/mailman/listinfo/p2p-hackers
