The modified DNS server would also need to track the port numbers for hosts behind NAT along with:
Table ( PublicKey, DynamicDNShostName, DynamicDNSipAddress (non static public routable), DynamicDNSipPortNumber, StaticTincIPaddress (5.0.0.0/8), StaticMacAddress 55:5dotIPaddress , MemberListOfTincNetworkNames, TTL, ??? ) On 3/6/09, Rob Townley <[email protected]> wrote: > Maybe I am missing something, but since each host already has a public > & private key, then why is a 3rd party needed currently? > > But it is difficult to replicate the public host file to each > machine. That is why I would welcome a modified myDns or modified > djbdns that holds the public key for each dynamically updated > hostname. Hamachi must use a special DNS server to accomplish this. > > > > On 3/6/09, Albi Rebmann <[email protected]> wrote: >>> For tinc 2.0> certificate based authorisation will be used that allows >> clients to authenticate each other without the need for a third party to >> be online. >> >> Are there news about tinc 2.0? >> Release date ;) >> >> >> ALBI... >> >> >> _______________________________________________ >> tinc mailing list >> [email protected] >> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >> > _______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
