[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-dev] Implications of openssl bug on directory authorities

To: tor-dev@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-dev] Implications of openssl bug on directory authorities
From: Nick Mathewson <nickm@xxxxxxxxxxxx>
Date: Mon, 14 Apr 2014 15:02:39 -0400
Delivered-to: archiver@xxxxxxxx
Delivery-date: Mon, 14 Apr 2014 15:02:53 -0400
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=QPCIxr6RW57LYpXDnBewM2D8kvqUWrTJENUM1XErhhE=; b=Toxrggls3UY0fj///TGbTax4Ns+jOYPNdFDh9SHLq/bnk0re2WAQaQV+4TJ0IUSBPR UCPx8HJhh6XYaiqMbKflLXCrRJoOy2PPr/tLj3QJSg7f/noBB+1H3hyIuEBb5dwepJUq kQBgTpHNntsn4O9K7OWqrGg2oJAonvYkGSJNCQIGL4XDt8Aq+6NuBIsiLZ6wG+qwmMAh TsFobSqAa9m6jLgL/Q6n1Gl1yCji5od7rBtFob6lcUt431Fv1o4nmzsj7dmXCQNgIOWa jV3Oa9Og8pMbxPOOy+wAVD7aXFYcq5KYZFnLxLrgumqGbgedkl+8Zd4JW3oG8YUxYbwg FMnw==
In-reply-to: <CAKDKvuwtQgm5P_JEq_tuRQnJ2iTS_mgB+ME=bwiKMPOqUQ4Q=w@xxxxxxxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-dev/>
List-help: <mailto:tor-dev-request@lists.torproject.org?subject=help>
List-id: discussion regarding Tor development <tor-dev.lists.torproject.org>
List-post: <mailto:tor-dev@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=unsubscribe>
References: <20140409094943.GM22584@xxxxxxxxxxxxxx> <CAKDKvuwtQgm5P_JEq_tuRQnJ2iTS_mgB+ME=bwiKMPOqUQ4Q=w@xxxxxxxxxxxxxx>
Reply-to: tor-dev@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-dev" <tor-dev-bounces@xxxxxxxxxxxxxxxxxxxx>

On Wed, Apr 9, 2014 at 8:36 AM, Nick Mathewson <nickm@xxxxxxxxxxxx> wrote:
> On Wed, Apr 9, 2014 at 5:49 AM, Roger Dingledine <arma@xxxxxxx> wrote:
>  [...]
>> Anybody have a plan 3?
>
> Update the client and server code to explicitly blacklist the old
> signing keys, and design a better key revocation mechanism for the
> next time, in case there is a next time?

I've got a draft patch for this up at
https://trac.torproject.org/projects/tor/ticket/11464 , but I need a
list of bad authority signing keys and/or certs.  Who can get me that?

cheers,
-- 
Nick
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Follow-Ups:
- Re: [tor-dev] Implications of openssl bug on directory authorities
  - From: Roger Dingledine

References:
- [tor-dev] Implications of openssl bug on directory authorities
  - From: Roger Dingledine
- Re: [tor-dev] Implications of openssl bug on directory authorities
  - From: Nick Mathewson

Prev by Author: Re: [tor-dev] Implications of openssl bug on directory authorities
Next by Author: [tor-dev] Proposal 232: Pluggable Transport through SOCKS proxy [was Re: ideas/xxx-pluggable-transports-through-proxy.txt]
Previous by thread: Re: [tor-dev] Implications of openssl bug on directory authorities
Next by thread: Re: [tor-dev] Implications of openssl bug on directory authorities
Index(es):
- Author
- Thread