Delivery-Date: Fri, 11 Dec 2015 19:52:45 -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_ADSP_CUSTOM_MED,
	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 3F4D71E0DFF;
	Fri, 11 Dec 2015 19:52:43 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DEF7E3884D;
	Sat, 12 Dec 2015 00:52:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 766BD38846
 for <tor-talk@lists.torproject.org>; Sat, 12 Dec 2015 00:52:35 +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 zenNUSHCgtkg for <tor-talk@lists.torproject.org>;
 Sat, 12 Dec 2015 00:52:35 +0000 (UTC)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com
 [IPv6:2607:f8b0:4001:c06::235])
 (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 46C8C38688
 for <tor-talk@lists.torproject.org>; Sat, 12 Dec 2015 00:52:35 +0000 (UTC)
Received: by iojd73 with SMTP id d73so25777288ioj.3
 for <tor-talk@lists.torproject.org>; Fri, 11 Dec 2015 16:52:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=kwRrKeHMQvvH8HJJWKSiG3ztuHItHaVFPBRS1MpDpO4=;
 b=Odi4TobP+AoNZemLmlsux/lPaW5GgzWAu10DD8eP219w6pzMYdzVtDHlt/OWm5/Bhr
 0Q5ogU+gosp7VjkGGoU+mhMMv+xHNC5+hGgV6/rIr1sfbHq4CZ/2sKYJlIhXpyjADEEo
 lyWAi39l4eQEKnHZBl6VC0MKPnoCSGfWviIToxT9cGM+q7kiEYVpqWU+6UYqVFAxrZe4
 a//J7zBm+cpmlsY9Nfw3qJAVKntqxdZpUyel3snKJIxEpYxx8KMPQjuKpHTlRO3/KvAU
 SSbSkAQekyGLvWiqjWYZrH9H9DPrSRSuGJZPZJbPITn8f2NLcAFzBXXncLLSofSDwZPG
 umnw==
MIME-Version: 1.0
X-Received: by 10.107.168.5 with SMTP id r5mr2097938ioe.126.1449881552800;
 Fri, 11 Dec 2015 16:52:32 -0800 (PST)
Received: by 10.107.157.9 with HTTP; Fri, 11 Dec 2015 16:52:32 -0800 (PST)
In-Reply-To: <mailman.23.1449835202.18013.tor-talk@lists.torproject.org>
References: <mailman.23.1449835202.18013.tor-talk@lists.torproject.org>
Date: Fri, 11 Dec 2015 19:52:32 -0500
Message-ID: <CAAJRmyOXfcSurxf-LimgvMa3sN+y-bHiBBYF4rD_EXDORvd0Dw@mail.gmail.com>
From: Marcel Rossler <rossler.marcel@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] tor-talk Digest, Vol 59, Issue 13
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>

I DO NOT UNDERSTAND WHAT THIS IS ALL ABOUT: tor-talk mailing list.
Could you please explain this to me in a not scientific language and to
tell me what I have to do to be protected?
Thanks in advance.

2015-12-11 7:00 GMT-05:00 <tor-talk-request@lists.torproject.org>:

> Send tor-talk mailing list submissions to
>         tor-talk@lists.torproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
> or, via email, send a message with subject or body 'help' to
>         tor-talk-request@lists.torproject.org
>
> You can reach the person managing the list at
>         tor-talk-owner@lists.torproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tor-talk digest..."
>
>
> Today's Topics:
>
>    1. Re: single entity running >36% exit probability with 5
>       relays? scary. (meejah)
>    2. Save Crypto: Tell the White House We Can't Sacrifice      Security
>       (grarpamp)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 11 Dec 2015 02:35:36 +0400
> From: meejah <meejah@meejah.ca>
> To: tor-talk@lists.torproject.org
> Subject: Re: [tor-talk] single entity running >36% exit probability
>         with 5  relays? scary.
> Message-ID: <86k2omx77r.fsf@atlantis.meejah.ca>
> Content-Type: text/plain; charset=us-ascii
>
>
> It seems there's "some" interest in upgrading TorFlow? I can't in good
> conscience say that -- without funding -- I alone can replace it -- but
> I do have an out-of-date txtorcon exit-relay scanning system that could
> *become* a "next gen" torflow.
>
> I am ready and willing to provide mentorship to make this happen.
>
> >From my perspective, the best-case would be a motivated and knowledeble
> student or intermediate programmer who is self-motivated and already
> versed in event-based programming (ideally Twisted, but asyncio,
> node.js, boost's asio or others are great too).
>
> IMO, the best thing would be for authority operators to enumerate on a
> wiki page or ticket a) their requirements and b) their issues with
> TorFlow. Or, I guess, c) torflow is amazing and meejah has the wrong
> impression :)
>
> Cheers,
>
> --
> meejah
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 11 Dec 2015 03:46:48 -0500
> From: grarpamp <grarpamp@gmail.com>
> To: cypherpunks@cpunks.org
> Cc: tor-talk@lists.torproject.org
> Subject: [tor-talk] Save Crypto: Tell the White House We Can't
>         Sacrifice       Security
> Message-ID:
>         <
> CAD2Ti29Ov7aavXEDfgmA+5kaGZM0WwDPhOms7oiaX9NWz6zW2A@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
>
> https://www.eff.org/deeplinks/2015/12/save-crypto-tell-white-house-we-cant-sacrifice-security
>
> https://petitions.whitehouse.gov/petition/publicly-affirm-your-support-strong-encryption
> https://www.whitehouse.gov/webform/share-your-thoughts-onstrong-encryption
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> tor-talk mailing list
> tor-talk@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>
>
> ------------------------------
>
> End of tor-talk Digest, Vol 59, Issue 13
> ****************************************
>
-- 
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

