Re: Easier reference swapping

Matthew Toseland wrote:
> On Mon, Mar 05, 2007 at 01:52:33PM -0600, David Sowder (Zothar) wrote:
>   
>> Colin Davis wrote:
>>     
>>> It solves #2- Don't run things you get in e-mail..
>>>
>>> Instead of requiring a Noderef, allow someone to connect with just a 
>>> password, and the IP address. This is something you can TELL someone, or 
>>> say in an IM, no file transfer required.
>>>   
>>>       
>> I don't think we should necessarily categorically discount a fred-based
>> installer distribution servlet because of NAT problems.  What if we
>> allow decoupling the installer from the noderef?  Then those that can
>> overcome or don't have the NAT problem can host the installer. 
>>     
>
> They are a sufficiently small fraction of the overall target audience as
> to be uninteresting. UP&P would make them a large enough group to be
> interesting, although still only something like 50% because UP&P is
> extremely unreliable from what I have heard.
>
>   
>> If I,
>> for some reason, cannot host the installer, perhaps one of my peers is
>> willing to share their installer hosting such that I could get "access
>> keys" from his node to pass out to my friends and include my noderef
>> from the distribution area of FProxy in the email I send to my friend
>> with the "access key".  My friend saves the attached noderef (which was
>> attached as a file with a .fref extension) to a file, connects to the my
>> peer's installer host, uses the "access key", which will probably be
>> part of the URL, and downloads and installs the node.  Then my friend
>> can double click on the .fref file he downloaded, which includes a
>> one-time code generated by the distribution area of my FProxy (or FCP
>> server) that my node uses to authenticate the addition of a node I
>> didn't already have the noderef of.  Node installed in a decentralized
>> way.  Peer connection created.
>>     
>
> This is not very clear. Please divide into what friend A does and what
> friend B does.
>   
Friend A (wanting to connect with Friend B) does:
1) Gets an installer URI (containing an "access key") from his node's
direct (or maybe even indirect mutual friend's) peer (C's)
2) Generates a one-time sharable noderef by asking his own node (A's)
via FProxy or FCP
3) Emails the installer URI from step 1 to Friend B (the
to-be-peered-with friend), attaching the .fref file generated in step 2

Friend B does:
1) Receives the email from Friend A
2) Saves the email attached .fref to disk'
3) Points a web browser at the installer URI from the email
4) Installs a Freenet node using the installer located at the installer URI
5) Double-clicks or otherwise uses the .fref file as configured for
Friend B's operating system by the installer to add Friend A's one-time
sharable noderef (it contains a code Friend A's node uses to
authenticate connection to a peer it didn't previously have a ref for)
6) Trades "normal" noderefs with others to add more peers to his node

Friend C does:
1) Gives Friend A permission and access to distribution area of their
node to generate installer URIs to be used by Friend B (and Friend A's
other friends)
2) Leaves the node up and running enough for Friend B to use the
installer URI to install a Freenet node

The roles of Friend A and Friend C could be combined in the case where
Friend A doesn't have NAT or has proper port forwarding and dyndns, in
which case a installer and noderef URI could be used instead. (Provides
the installer and connects to the node created by the installer it
provided.)