Re: [Doh] Running code

manu tman <chantr4@gmail.com> Thu, 11 January 2018 20:19 UTC

Return-Path: <chantr4@gmail.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEBD412E034 for <doh@ietfa.amsl.com>; Thu, 11 Jan 2018 12:19:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQeoCg9OyExm for <doh@ietfa.amsl.com>; Thu, 11 Jan 2018 12:19:22 -0800 (PST)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94C3F12EC3C for <doh@ietf.org>; Thu, 11 Jan 2018 12:19:22 -0800 (PST)
Received: by mail-qt0-x22d.google.com with SMTP id u42so3407838qte.7 for <doh@ietf.org>; Thu, 11 Jan 2018 12:19:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZgyYgL6+QuN+iKK0EOBxg9d4QNkw+v2WmWNUOWAh6rc=; b=UF4B0I+T6BUu3vXoKR58EvJtamLG4TbQMatzjFPKKmC8Tn5ePo9JCwOyyP1bejKLCX oAmW3BLGjRgIb8nrAauuuZUbGe2AhkoG/ZaEQup2d6BXfQbT6uyQWBqWQYZKxVpLCmba OCK2651lMeX+vFuT24Gjrn383NvC7AsBx5Y0Ly4vhS73GQQXHkp6YmK72YHs/wvzpTtx 4RaZ7p+SANjXRVVsbGNOXfqPXwV4faIH4R06DVj/7N+B/MgSoWxLuz66Zbe3WJ9gH4QP tvgauWMTuWkx/URCQjyA73Kn1K2T0z2gj0TmqnObN1hJHD309Wrv9ltCeZhqeoCUj/rh 41wg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZgyYgL6+QuN+iKK0EOBxg9d4QNkw+v2WmWNUOWAh6rc=; b=B1HD1w6AKd+mT+Ifela9vsqTxLsbtpIaUIgkdJIMSz0szm8O8LgvebVdXznx7k3Y9o Zngw67a1F6PVCwyLDcuYSGdNgyYjqlnzmfnv/q3JO7sUNtPVqt2/IxJ2Il+RksZWGu0l izieCCebS8V7lIc74LtazMjqM4dYhN7mqH0svCSxoClVl3z4tsChjLPjkMS1joH4MLvZ BGnRCD3Dp8JkJaOIMC2cz//Vd2+p1dckMwCxQ1tVaZoAWZJkEecxitfid5W/I5orEunc ORYw1SvvRtDQq2aGUbu8jvesoWRdeuPUfvqNGDkCS5DMtQGCtVcWH/QUkWz0nzr550kV mnzA==
X-Gm-Message-State: AKwxytf2xpkVC9GCPn//iH7fOInHwPiR7JoTVnYnXSJzsd/plqJgm+gw jA0S3hh470+NCwDNaBFLKufuhcf9+S0J2y77SNo=
X-Google-Smtp-Source: ACJfBoumHj5+SXivGBmQhRgdW+Rv/q2iBxyUnC5fr+gzxeA35PTz5NQ/9U/bIEJFmPUSjV9wzs/fXaBWQGx4oGPIP3A=
X-Received: by 10.200.55.227 with SMTP id e32mr1128117qtc.158.1515701961592; Thu, 11 Jan 2018 12:19:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.35.136 with HTTP; Thu, 11 Jan 2018 12:19:21 -0800 (PST)
In-Reply-To: <CAArYzrK_k+PDPx9GCRbD03P+mdY6fEtKUn-khCHbzj5EQA4Q1A@mail.gmail.com>
References: <CAHbrMsAyEA2=RmS3NUSA-agZ5A-vWxE9E0iUMbcLgHQ2S4estA@mail.gmail.com> <CAArYzrK_k+PDPx9GCRbD03P+mdY6fEtKUn-khCHbzj5EQA4Q1A@mail.gmail.com>
From: manu tman <chantr4@gmail.com>
Date: Thu, 11 Jan 2018 12:19:21 -0800
Message-ID: <CAArYzr+VZvqNH-kCoCtJicOjCTzrGmdzqg-6suVcwqE_5z+B1g@mail.gmail.com>
To: Ben Schwartz <bemasc@google.com>
Cc: doh@ietf.org
Content-Type: multipart/alternative; boundary="001a113ee1cc0195d5056285dddf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/WAnacYLv5GHmvzIvSmpSZF_A3eI>
Subject: Re: [Doh] Running code
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 20:19:25 -0000

Hi all,

Following up on Ben's announcement of a "publicly" available DOH server, I
brushed up some of the work I did during IETF 100 Hackathon and pushed the
changes to https://github.com/facebookexperimental/doh-proxy . This is best
effort support, but feel free to file tasks and/or submit PRs.

TL;DR if you have at least python 3.5, you can get the tool from pypi
directly:
```
pip3 install doh-proxy
doh-stub  --listen-port 5553 --domain dns.google.com --remote-address
216.58.193.78 --uri /experimental
```

And the test with `dig @127.0.0.1 -p 5553 ....`

Manu

On Wed, Jan 10, 2018 at 7:26 AM, manu tman <chantr4@gmail.com> wrote:

> Great stuff!
>
> I tried the client and stub I implemented during IETF 100 hackathon [0]
> against it.
> After some minor changes (configurable DOH_URI and using ct instead of
> content-type parameter, the client (which is just performing 1 query) is
> working, but the stub is not. It seems that aioh2 client is not working
> correctly with http2 servers in general, not just dns.google.com (other
> than its own). I will dig into this when times permits and update the code
> and this list.
>
> Manu
>
> [0] https://github.com/chantra/doh-proxy
>
> On Tue, Jan 9, 2018 at 3:11 PM Ben Schwartz <bemasc@google.com> wrote:
>
>> Hi DOH,
>>
>> As a DOH participant, I've been working on an implementation
>> of draft-ietf-doh-dns-over-https-02, and I'm happy to report that it's
>> now available at https://dns.google.com/experimental.  For example, you
>> can test the example from Section 5.2 by running
>>
>> wget 'https://dns.google.com/experimental?ct&body=
>> q80BAAABAAAAAAAAA3d3dwdleGFtcGxlA2NvbQAAAQAB'
>>
>> This service is experimental, and is not intended to support a large
>> volume of queries.  We may make compatibility-breaking changes to keep up
>> with this working group's drafts, and we will likely shut it down (and move
>> it to a more permanent path) if and when the working group reaches
>> consensus on the protocol.
>>
>> I hope this service is useful to DOH participants who are working on
>> clients.  I also hope anyone who encounters a bug in this implementation,
>> or a deviation from the draft, will let me know.
>>
>> --Ben Schwartz
>> _______________________________________________
>> Doh mailing list
>> Doh@ietf.org
>> https://www.ietf.org/mailman/listinfo/doh
>>
>