Re: [GNUnet-developers] question on how to enforce anonymity

[j-t muyl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> The simplest way would be to add an option that disables receiving new HELO
> advertisements (expiration-refresh should be allowed) from other peers and
> then just manually (IRL) exchanging the files from data/hosts.  That way,
> the respective peers would be limited to hosts that were explicitly added
> to their data/hosts file.  I've committed (and attached) a 2-line patch
> that adds the respective option (but read the comment: no NAT, change
> HOSTLISTURL).
>
> But I would not call such a feature "enforcing anonymity" since you're now
> trusting a small circle of "friends" and possibly are making a traffic
> analysis easier since you are limited in your connections.
>
> Christian

Hum, i understand what you mean. it is more anonymous in the way that nobody 
expect your friends know you use gnunet and you can't become tricked.
I thought about the question of traffic analysis, and I think that with strong 
specific encryption between two nodes (strong RSA, or even OTP with IRL 
key-exchange, stegano of crypted datas in video-audio stream, we can imagine 
an infinity of parano-solutions :P), it is more anonymous to communicate with 
trusted-nodes, than exchanging and diffusing IPs over the net..
In all cases, let's give the choice to the user ! I'm actually looking at the 
CVS-source, and configuring the 0.6.1d. 

JT

- -- 
http://lea-linux.org
Ce message a été rédigé au moyen de Logiciels Libres.
Clé pgp : http://maston28.homelinux.org/maston28.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAe/FofyEsDW0wqT4RAhnBAJ4tnzeogmGT74Uy8PofhfItJ4+QbACfVe0j
Qs32xDTLsf7zos3l8kvsMYk=
=MoBy
-----END PGP SIGNATURE-----