Re: [tor-dev] Prop279 and DNS

2017-04-29 Thread Jeremy Rand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hugo Landau: > After giving it some thought, I think Tor should use a > Tor-specific protocol to interface with name plugins, not DNS. > > My reasoning is as follows: the Tor daemon knows what it wants and > is designed to source specific data from

Re: [tor-dev] Prop279 and DNS

2017-04-26 Thread Hugo Landau
After giving it some thought, I think Tor should use a Tor-specific protocol to interface with name plugins, not DNS. My reasoning is as follows: the Tor daemon knows what it wants and is designed to source specific data from a name plugin. Where Tor specifies a custom protocol for this, this will

Re: [tor-dev] Prop279 and DNS

2017-04-24 Thread meejah
Jeremy Rand writes: > AFAIK there aren't any good Python libraries for this kind of thing > (at least, none that support DNSSEC), though it's been a year or so > since I last looked. Twisted has a DNS server and client implementation. I'm not sure where it stands on DNSSEC support, although a qu

Re: [tor-dev] Prop279 and DNS

2017-04-23 Thread Jeremy Rand
George Kadianakis: > Hmmm, > > using DNS for the query/resolve part of the NS API might actually be a > reasonable approach for Tor. Prop279 is currently doing query/resolves > using stdin/stdout messages but people have rightly pointed out that > this sucks in mobile platforms: >https://l

Re: [tor-dev] Prop279 and DNS

2017-04-06 Thread Jeremy Rand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Jesse V: > On 04/03/2017 05:01 PM, Jeremy Rand wrote: >> Maybe this topic has already been brought up, but in case it >> hasn't, I'll do so. I notice that Prop279 (onion naming API) >> defines its own API rather than using DNS. I guess that this is

Re: [tor-dev] Prop279 and DNS

2017-04-05 Thread George Kadianakis
Jeremy Rand writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hello! > > Maybe this topic has already been brought up, but in case it hasn't, > I'll do so. I notice that Prop279 (onion naming API) defines its own > API rather than using DNS. I guess that this is because of securit

Re: [tor-dev] Prop279 and DNS

2017-04-03 Thread Jesse V
On 04/03/2017 05:01 PM, Jeremy Rand wrote: > Maybe this topic has already been brought up, but in case it hasn't, > I'll do so. I notice that Prop279 (onion naming API) defines its own > API rather than using DNS. I guess that this is because of security > concerns about the centralization of the

[tor-dev] Prop279 and DNS

2017-04-03 Thread Jeremy Rand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello! Maybe this topic has already been brought up, but in case it hasn't, I'll do so. I notice that Prop279 (onion naming API) defines its own API rather than using DNS. I guess that this is because of security concerns about the centralization