On 11/04/2016 06:46 PM, Martin Schanzenbach wrote: >> > This summer I reported https://gnunet.org/bugs/view.php?id=4625 >> > >>> > > >>> > > For many kinds of applications we need to authenticate incoming >>> > > connections as coming from a certain person or at least from a >>> > > certain peer. The exit daemon is currently not providing a way to >>> > > find out who is calling. Resolving the virtual IP number would be >>> > > the most backward compatible method. Best if it resolves to the >>> > > same "hostname" as the matching outgoing <nickname>.gnu, or even >>> > > uses the same virtual IP as an outgoing VPN tunnel would use. >> > > Yes, this is what reverse resolution is for. The only thing you can > know about the "caller" is his peerid/identity, at best. > Now, the question is how you find a path from _your_ identities to that > peer. The other way around not necessarily useful.
We need to distinguish: * reverse resolution of a (VPN) IP address to GNS name * reverse resolution of GNS Zone key to GNS name You are both confusing / confounding the two. In my view, they are likely to require very different methods to tackle.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
