IETF Logo Mail Archive

Re: [dsfjdssdfsd] what not to do...

Donald Eastlake <d3e3e3@gmail.com> Wed, 02 April 2014 14:58 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: dsfjdssdfsd@ietfa.amsl.com
Delivered-To: dsfjdssdfsd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A87B01A0249 for <dsfjdssdfsd@ietfa.amsl.com>; Wed, 2 Apr 2014 07:58:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XxEtOn0RXAsy for <dsfjdssdfsd@ietfa.amsl.com>; Wed, 2 Apr 2014 07:57:59 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id E6F6E1A0257 for <dsfjdssdfsd@ietf.org>; Wed, 2 Apr 2014 07:57:58 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id wm4so373651obc.3 for <dsfjdssdfsd@ietf.org>; Wed, 02 Apr 2014 07:57:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CQCscKRTuChoZ6bIV2E5dLcmYKbd7PeKqKzgkJ6ipXM=; b=ixAY1kpjSoA0P/SanS889lTosbqxYiNlfY+VoMJroGfkJ/2p+gBY/gIUiB5NH7hI/y nNA71mdRfo2fpfAHTc2KmGyX+F+rbsKWUhgD2CCm8BURv843JAO+5gUAzwRzJqMLhQaN qFdSx+EQxQ6Zo4gdfgs8UXM2ucIHKFhUKhT1ydZTpB30I7pU1C1sS7yw8A9svfsQaNQs 8/ZS0P9CpL8tTGCoMEv3dy3C9PX6kPPzbBOcJ6IeWl1C6+Zc56sVAMXCk/Ph2CidWRzX shnmUEJJ1Q9s1xKAPKOtTcleBqyNWzNxTBdKa4fXTTN2PdMBb81Yo4SJTMWaO51nQ7V3 7d6g==
X-Received: by 10.60.40.103 with SMTP id w7mr352118oek.57.1396450674928; Wed, 02 Apr 2014 07:57:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Wed, 2 Apr 2014 07:57:34 -0700 (PDT)
In-Reply-To: <CACXcFm=ts6JWuW+pQtaqZ720QDxnEa22UZW2NiBYMgCCV7MPuw@mail.gmail.com>
References: <533AF317.5070901@cs.tcd.ie> <CACXcFm=ts6JWuW+pQtaqZ720QDxnEa22UZW2NiBYMgCCV7MPuw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 02 Apr 2014 10:57:34 -0400
Message-ID: <CAF4+nEF8N5C7zmGh5TBnp29zP1Fi2PMzoU4x4EEH8hY82PnS0w@mail.gmail.com>
To: Sandy Harris <sandyinchina@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/dsfjdssdfsd/lcbZH63PhcrpYla3F-a496rsQNo
Cc: "dsfjdssdfsd@ietf.org" <dsfjdssdfsd@ietf.org>
Subject: Re: [dsfjdssdfsd] what not to do...
X-BeenThere: dsfjdssdfsd@ietf.org
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." <dsfjdssdfsd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dsfjdssdfsd>, <mailto:dsfjdssdfsd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dsfjdssdfsd/>
List-Post: <mailto:dsfjdssdfsd@ietf.org>
List-Help: <mailto:dsfjdssdfsd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dsfjdssdfsd>, <mailto:dsfjdssdfsd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 14:58:02 -0000

Hi,

Yes, the "bad ideas" section of RFC 4086bis
(draft-eastlake-randomness3-00) seems like a good place to collect
additional things not to do.

I am planning to update that draft soon...

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Wed, Apr 2, 2014 at 10:24 AM, Sandy Harris <sandyinchina@gmail.com> wrote:
> On Tue, Apr 1, 2014 at 1:10 PM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
>
>> It seems like there's a lot of knowledge on that spread
>> about and if there was someone was willing and able maybe
>> an informational RFC about mistakes that have been made
>> and how implementers can avoid 'em might be useful.
>
> I think the old RFC 1750 and current 4086 pretty much cover that.
> https://tools.ietf.org/html/rfc4086
>
> There has been mailing list discussion of an update to 4086, but
> I do not know how that is progressing.
>
>> Or maybe there's a survey paper out there somewhere
>> or thesis that already has a load of that material?
>
> At least two reference pages have been mentioned on
> various lists. I have looked at two and found both quite
> good. Unfortunately, I only recall one URL:
> http://www.av8n.com/computer/htm/secure-random.htm
>
> _______________________________________________
> dsfjdssdfsd mailing list
> dsfjdssdfsd@ietf.org
> https://www.ietf.org/mailman/listinfo/dsfjdssdfsd

v2.23.0 | Report a Bug | By Email