> Not all routers work like that. It seems mine doesn't any more after having reset it, so I would have to concur.
> > 'self' is the new servlet I proposed > > Servlets don't run on FNP. You mean a FNP packet. Sorry, good point. > A needs to ask another node to do the verifying. With the router behaviour, I would have to agree. I have difficulty envisaging a solution that would work when B and 'C' are two aliases for the same node (maybe a multihomed node?). Of course, with a large set of node references to choose from, just picking a random node C!=B is probably good enough. 1. A->B what is my IP 2. *B*->*C* ask this IP for a self check 3. *C*->A Your IP address appears to be aaa.bbb.ccc.ddd - what is your encrypted message (A rejects if this appears to come from node B) 4. A->C here is my encrypted message 5. C->B here is A's encrypted message 6. B->A here is your encrypted message and your IP address appears to be aaa.bbb.ccc.ddd (A rejects if IP address in 3 doesn't match IP address in 6) With suitable timeouts on waiting for replies, and of course A creating new keypairs and encrypted messages each time it asks a node for its IP. Any thoughts? Too much hassle to be worth it? d _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
