Delivery-Date: Tue, 26 Jan 2016 07:03:56 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id AFC4E1E01B4;
	Tue, 26 Jan 2016 07:03:54 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0EA1534BEB;
	Tue, 26 Jan 2016 12:03:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5773C217B9
 for <tor-talk@lists.torproject.org>; Tue, 26 Jan 2016 12:03:46 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 0v6J38CUh-a9 for <tor-talk@lists.torproject.org>;
 Tue, 26 Jan 2016 12:03:46 +0000 (UTC)
Received: from forward18p.cmail.yandex.net (forward18p.cmail.yandex.net
 [77.88.31.38])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 223D5215DC
 for <tor-talk@lists.torproject.org>; Tue, 26 Jan 2016 12:03:46 +0000 (UTC)
X-Greylist: delayed 669 seconds by postgrey-1.34 at eugeni;
 Tue, 26 Jan 2016 12:03:46 UTC
Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [95.108.252.17])
 by forward18p.cmail.yandex.net (Yandex) with ESMTP id 40463217BA
 for <tor-talk@lists.torproject.org>; Tue, 26 Jan 2016 14:52:33 +0300 (MSK)
Received: from smtp17.mail.yandex.net (localhost [127.0.0.1])
 by smtp17.mail.yandex.net (Yandex) with ESMTP id F3C891901EE0
 for <tor-talk@lists.torproject.org>; Tue, 26 Jan 2016 14:52:32 +0300 (MSK)
Received: by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id
 Lps73nyYcy-qUXaX935; Tue, 26 Jan 2016 14:52:31 +0300
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client certificate not present)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail;
 t=1453809152; bh=cxxKKNsNGV0OmrZp4B6FdywHgCt2J6ARxvrODU7zNgI=;
 h=Date:From:To:Subject:Message-ID:In-Reply-To:References:X-Mailer:
 MIME-Version:Content-Type:Content-Transfer-Encoding;
 b=AcszHUyZrJyIs9h5Lb+XqyB2ntXDXIra05VjLpci3V1lH2NkC8Tb2qJhVK9gl2Z1V
 64rHi8rdjcrV6ET50O2cHy5gldHkFUmj0PyW+IBn3ZIu+oHiuBu9CJZb8gEJ1KaLUU
 ejnDLMiWwyVzIgo8clK0zHM2kWynvIWVphE7pcT0=
Authentication-Results: smtp17.mail.yandex.net; dkim=pass header.i=@yandex.com
X-Yandex-ForeignMX: US
Date: Tue, 26 Jan 2016 21:52:09 +1000
From: Katya Titov <kattitov@yandex.com>
To: tor-talk@lists.torproject.org
Message-ID: <20160126215209.0e6a4183@localhost.localdomain>
In-Reply-To: <CAP-cguVXdvcDJKgLHb8o_5MjfFzvt1+Gtaiw1G7NUm9QtgbBXw@mail.gmail.com>
References: <CAP-cguVXdvcDJKgLHb8o_5MjfFzvt1+Gtaiw1G7NUm9QtgbBXw@mail.gmail.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Subject: Re: [tor-talk] Onion service discovery
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Joshua Hull:
> I've been thinking about how to get onion services transparently
> selected over non-onion services in order to drive adoption. It seems
> to me that a simple strawman proposal would be that before attempting
> to connect to a domain name, do a lookup for a specific type of TXT
> record, ensure it's being served over DNSSEC, and if both things are
> true, prefer that record.

Check out Darkweb-Everywhere, a fork of HTTPS Everywhere, and the
associated email thread:

https://github.com/chris-barry/darkweb-everywhere/releases
https://lists.torproject.org/pipermail/tor-talk/2014-February/032220.html

> However, I can't seem to find much documentation on preferred
> mechanisms for discovering onion services. Is there something similar
> to the scheme I mention above already in use that someone could point
> me to?

Hopefully someone else can answer this. I've run hidden services and
can confirm that they can be discovered, but I'm not sure on the
best/preferred discovery methods.

-- 
kat
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

