Re: [freenet-dev] Easier reference swapping
Matthew Toseland <toad-EI5O+8PHWbJeeLb3ft/[email protected]>
| Newsgroups | gmane.network.freenet.technical |
|---|---|
| Message-ID | <[email protected]> |
Okay, the below could work (you have to include the port number though). However in an ideal world we would like to be able to eliminate the callback stage (B telling A his password) altogether; then A could simply give B a CD-ROM containing the node plus a one-time reference; B runs this, and it Just Works. On Mon, Mar 05, 2007 at 03:49:17PM -0500, Colin Davis wrote: > I'm sorry that I'm being dim- > Could you please explain how the network topography is exposed? I'm sure > you're right, I'm just missing it. > > > > > > If we have two clients, A and B, who want to talk to one another.. Both > are behind Firewalls.. > > * A calls up B, and tells him "Connect to me, at 11.22.33.44, password > 'Bob is a super cool password'" > > * B Says sure, and clicks the "Connect to a new client" icon in Fred, > enters the IP and Password. > > * B's machine starts sending Freenet packets to A, thus opening up a NAT > hole to his machine through the UDP trick. > > * B then tells A "It's running! Add my computer back. Mine is > 22.33.44.55, and the password is 'Donkeys are really cool, and I like > the way they look' " > > * A adds B's IP and password, and starts sending freenet packets to B. > * A's machine is now exposed, through the UDP trick. > > * B's packets, which he is still sending, get through. > * A's packets get through to B. > > * Now that they're talking, they exchange signed keys (real noderefs), > so next time, they don't need to do the passwords. > > * Fred disables the passwords. > > Nothing has required the use of a third party, other than the telephone > call between the two of them to share the passwords. > > -Colin > > > > > >> When Side-A added the noderef of B, it would start sending out packets > >> to B, knowing that they won't get returned.. But the Sending of these > >> packets would open a NAT-hole.. > >> Then, Side-B would get around to adding the noderef of A, and start > >> sending packets to A, opening a NAT-hole on their own side.. Side A's > >> packets then get in through this hole, just as B's now arrive at A. > >> > >> What am I missing? > >> > >> -Colin > > > _______________________________________________ > Tech mailing list > [email protected] > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech > _______________________________________________ Tech mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF7KFPA9rUluQ9pFARAntxAJ9rxJOTibcAFCr4UQ+T04mTG0Jq5wCfd1ij aCfWFLhvYiKB3KV13knTnUg= =m4YD -----END PGP SIGNATURE-----