Kjell Rune Skaaraas ([EMAIL PROTECTED]) wrote: > Case A: You get a connection from IP 80.23.53.56, > saying "contact me on IP 80.23.53.56, port 2334"
> Case B: You get a connection from IP 80.23.53.56,
> saying "contact me on my IP, port 2334."
Announcements are passed deeper than one hop. My node might get a
connection from 80.23.53.56 saying "There is a node at 90.33.23.18
port 12345; please pass this along to 7 more nodes." I don't know
whether 80.23.53.56 originated the request or got it from someone
else; I don't need to know that.
So what we have is this (if I understood your point correctly):
Current Freenet:
* Node must know its own IP address somehow. (Doesn't always work.)
Greg's Proposal:
* New node asks two other nodes what its own IP address is.
Kjell's Proposal:
* Announcements are done through a surrogate who will fill in
the original node's IP address and pass the announcement along.
I don't know enough about the announcement protocol itself to be able
to refute the last proposal. My first, instinctive reaction is that
it's vulnerable to some sort of attack by a hostile surrogate node, but
I can't come up with the actual attack itself. (It can't be an
anonymity compromise, because the announcement is *intended* to reveal
the origin's IP address and port number....)
--
Greg Wooledge | "Truth belongs to everybody."
[EMAIL PROTECTED] | - The Red Hot Chili Peppers
http://wooledge.org/~greg/ |
pgp00000.pgp
Description: PGP signature
