Re: [dsfjdssdfsd] Discussion: Malicious Entropy Attacks: Eggs, and Baskets Sun, 16 March 2014 17:17 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 08CB61A0301 for <>; Sun, 16 Mar 2014 10:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id q4_S6sXAXpAS for <>; Sun, 16 Mar 2014 10:17:30 -0700 (PDT)
Received: from ( [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by (Postfix) with ESMTP id 72A0C1A02F2 for <>; Sun, 16 Mar 2014 10:17:30 -0700 (PDT)
Received: from root ( by with local-esmtp (Exim 4.80) (envelope-from <>) id 1WPEga-0007iD-Pj; Sun, 16 Mar 2014 17:17:20 +0000
Received: by (Postfix, from userid 15806) id 353875802B0; Sun, 16 Mar 2014 13:17:16 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail; t=1394990236; bh=o7tlg7yDjPHqY0/A88An7HmDh5+xe01xt0J3fW3ZGDM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Z33s+770PWrR2r86+R6Ac8r6MQ0481kW3+Ygj8GlPNZkVRSxhqFx88atoEX28pQIG yrl9wRzWvWBYe34qEA9rl04cOVunig4CJIT00/S2XSRWR5NsaVjKtVFpIcszFr8fWj MH7/379IdC5o4oUzmwnl5SwrGNpFDzapKcYNDUUM=
Date: Sun, 16 Mar 2014 13:17:16 -0400
To: Arnold Reinhold <>
Message-ID: <>
References: <> <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.5.22 (2013-10-16)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Cc:, "Krisztián Pintér <>"
Subject: Re: [dsfjdssdfsd] Discussion: Malicious Entropy Attacks: Eggs, and Baskets
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The dsfjdssdfsd list provides a venue for discussion of randomness in IETF protocols, for example related to updating RFC 4086." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 16 Mar 2014 17:17:32 -0000

On Sun, Mar 16, 2014 at 11:18:29AM -0400, Arnold Reinhold wrote:
> And note that not all the issues I raised are software
> related. Tempest, for example, is a very tricky business. The NSA
> specs for Tempest protection are not publicly available, but I have
> been told they require tight physical configuration control, as even
> a single wire change can destroy Tempest protection.  Perhaps the
> best that can be achieved is to keep any attacker a safe distance
> from critical systems. A determined attacker might be willing to
> absorb the effort and risk to covertly penetrate physical security
> barriers if doing so will lead to a permanent compromise of a
> one-time-seeded PRNG, less so if the benefits will last only briefly
> as the PRNG reseeds after they leave.

One of the things which is not obvious is whether or not each
contributor has the same threat model in mind.  (In fact, it seems
pretty obvious to me that we don't all share the same threat model,
but I'm trying to be polite.  :-)

The sort of things that you might need to worry about if you are
trying to protect against pervasive monitoring are very different if
you are worried about a targetted attack.  If someone is willing to
bring in a listening truck and park it outside your house, or coverly
penetrate physical security, there is a whole host of things that you
would need to protect against before you are fully protected against
that level of attack.

In particular, who cares about how carefully constructed your RNG
might be if the attacker can replace it (along with perhaps your
entire networking stack, and the monitoring tools that might allow you
to notice that something strange has happened to your system)?  Or
just simply drop in some malware which leaks the session key after
your perfect RNG that meets with all of the academics' worries about
state compromise recovery....

						- Ted