Delivery-Date: Mon, 15 Feb 2016 10:01:46 -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,
	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 B08AC1E0AB3;
	Mon, 15 Feb 2016 10:01:44 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 07D0B3907E;
	Mon, 15 Feb 2016 15:01:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 921F339093
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 15:01:32 +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 LdUfPoyUm3e1 for <tor-talk@lists.torproject.org>;
 Mon, 15 Feb 2016 15:01:32 +0000 (UTC)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com
 [IPv6:2607:f8b0:4003:c01::231])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 68E963907E
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 15:01:32 +0000 (UTC)
Received: by mail-ob0-x231.google.com with SMTP id gc3so114152547obb.3
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 07:01:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:content-type;
 bh=2bC4Wg2vF5mMSZ3cjlK1mQvWXkHvz4dwGe/rmEZEmZ0=;
 b=Mn02Wp1cQp+F4sr/jukxImMi8JspP5q9CWNxVQWQNFMXisyVxeprECGjmOshLgtVDz
 OyuYCQjY64DwtXXv94Y1h+fSVaJ7FEFNgyjtLLKJOU8ukeBP889AWh3+aHRF86YkPM5c
 qSl5n3XYxcoPyz0SMWhcgAfmqZdGESEMxnFQR1fGEXMuIQkYiJLUO6AiUK62NJFvxwjN
 WmiFnk2VFQnndcX/CCerPPPraWpDFgm7eb0wO4J5cSnFIBX6/viG8hB4eGB9CBpTwG80
 K7WH3RoW5NkBGVEuXpEgaMe/sdTuuXjbIAm9e5h7JQCritc9vhUaS0vsmg+E7Db8vBCp
 vS4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:sender:in-reply-to:references:date
 :message-id:subject:from:to:content-type;
 bh=2bC4Wg2vF5mMSZ3cjlK1mQvWXkHvz4dwGe/rmEZEmZ0=;
 b=JgxzO3cAFIlkO/HRAYkv5ujSTW4NUgy/89tJnebwaVfDUCUXxgSI87SGCp/9ftyCSI
 CeC4GLnYHwy86hbHpVRwQJTSh2iHTaMMkXBT+e4rmINR0xnAW0jDrIpWInmvzDOglH+j
 +/mSv3HJKl3y1arXDTC23kzW7lZAYlQSkTwQnXPMUpXpGvKgKA4JuDYLYaAtIibW9lci
 Ap6jlj2b4WSrZjkwCRORvheen7GNWR0tBwhTI4zIMtgB+nAj7HfHVpno/g5axcy3dKIa
 0WAp8TbQiaKyN7j2AN8tkMwQQwOKkV/2A2esnINkY1OHwRxIls91APt7Y8njVXzZIAO0
 fGKA==
X-Gm-Message-State: AG10YOT3mMS+b+XZqrQdK1n4DrvHnCve7Ej6tem/4hxs/pGozl9ng6a0GqLYoo2AdIGqWjAOknhKngPToIRM+w==
MIME-Version: 1.0
X-Received: by 10.182.219.228 with SMTP id pr4mr13045343obc.52.1455548490015; 
 Mon, 15 Feb 2016 07:01:30 -0800 (PST)
Received: by 10.202.72.196 with HTTP; Mon, 15 Feb 2016 07:01:29 -0800 (PST)
In-Reply-To: <56C1BBA9.5040807@beroal.in.ua>
References: <56C1BBA9.5040807@beroal.in.ua>
Date: Mon, 15 Feb 2016 07:01:29 -0800
X-Google-Sender-Auth: vqkGNOjh8hI8UnxqeEOjl-fh06c
Message-ID: <CAJdkzEMKOWPgivw3w++9p6X2-75EpBO-6KK58Qr3u2Ff9G8J5g@mail.gmail.com>
From: Damian Johnson <atagar@torproject.org>
To: Tor Mailing List <tor-talk@lists.torproject.org>
Subject: Re: [tor-talk] Does Tor support ControlSocket?
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>

For what it's worth you might find the following helpful...

https://stem.torproject.org/faq.html#i-m-using-a-controlsocket

Cheers! -Damian


On Mon, Feb 15, 2016 at 3:51 AM,  <me@beroal.in.ua> wrote:
> Hi. Some old discussions on "stem" and "vidalia" suggest that Tor may be
> controlled via a Unix domain socket. This seems like a good way to control
> Tor on Unix; I just need to add a user who will control Tor to the "tor"
> group. But I can't find anything like a documentation.
> --
> 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
-- 
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

