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

Watson Ladd <watsonbladd@gmail.com> Wed, 02 April 2014 15:18 UTC

Return-Path: <watsonbladd@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 9500A1A0290 for <dsfjdssdfsd@ietfa.amsl.com>; Wed, 2 Apr 2014 08:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, 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 2HvlaMEcy8KB for <dsfjdssdfsd@ietfa.amsl.com>; Wed, 2 Apr 2014 08:18:24 -0700 (PDT)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id BB54A1A028E for <dsfjdssdfsd@ietf.org>; Wed, 2 Apr 2014 08:18:11 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id a41so352164yho.18 for <dsfjdssdfsd@ietf.org>; Wed, 02 Apr 2014 08:18:07 -0700 (PDT)
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 :cc:content-type; bh=M0N5rgBnNEQzA4a9BAwv45b7BRgEbCTcsH/Mru1Aq7g=; b=Z8KXsxExKfMu4oc6c6XpAqS4soV9q84njJe1bMr/8vHRMoo7ILqDn4HzUWOK7ToddV L+nHJWeC0YXFlxwjIfw/d4wBcEn55Cee0YNdc0nQf89PXPA9fu21ftGJTAwzJY7It+Tl lrQQ6IOf+RuCYdTF1odHW4Cit4O3Oxnw8Re7gz4qnmc12cCGISsSbEjK3pxKv4LFer9+ obdmHL7FLOV6EQsh+mHxR/CpPulrfHmicqzUGnm6Q3xcd/iXSIToxZ5NooESZtkObPJK MsezEgSRHaPeOEtogPhg4GvhGwf9Y51B04AW70xj1+rvEv/Vc1wtQhO9pHjAEu7wpfVf TFaA==
MIME-Version: 1.0
X-Received: by 10.236.120.66 with SMTP id o42mr1579590yhh.66.1396451887809; Wed, 02 Apr 2014 08:18:07 -0700 (PDT)
Received: by 10.170.63.197 with HTTP; Wed, 2 Apr 2014 08:18:07 -0700 (PDT)
In-Reply-To: <CAF4+nEF8N5C7zmGh5TBnp29zP1Fi2PMzoU4x4EEH8hY82PnS0w@mail.gmail.com>
References: <533AF317.5070901@cs.tcd.ie> <CACXcFm=ts6JWuW+pQtaqZ720QDxnEa22UZW2NiBYMgCCV7MPuw@mail.gmail.com> <CAF4+nEF8N5C7zmGh5TBnp29zP1Fi2PMzoU4x4EEH8hY82PnS0w@mail.gmail.com>
Date: Wed, 2 Apr 2014 08:18:07 -0700
Message-ID: <CACsn0c=x3K3NDHve3sKvaFuk_08Xp+wepPN=nkj00bLKNyOK0A@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dsfjdssdfsd/x70SXfCnSKxBhhkIkuU0gXdLqhs
Cc: "dsfjdssdfsd@ietf.org" <dsfjdssdfsd@ietf.org>, Sandy Harris <sandyinchina@gmail.com>
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 15:18:27 -0000

On Wed, Apr 2, 2014 at 7:57 AM, Donald Eastlake <d3e3e3@gmail.com>; wrote:
> 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.
>

No. Do not enumerate badness. Instead model correct behavior. You will
not be able to list all the ways someone can make a mistake, but you
can explain a way to do things right. The current draft is also
missing a discussion of the impact of fork and threading on random
number generators, which can turn a perfectly working one into
something utterly broken.

Sincerely,
Watson Ladd

> 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
>
> _______________________________________________
> dsfjdssdfsd mailing list
> dsfjdssdfsd@ietf.org
> https://www.ietf.org/mailman/listinfo/dsfjdssdfsd



-- 
"Those who would give up Essential Liberty to purchase a little
Temporary Safety deserve neither  Liberty nor Safety."
-- Benjamin Franklin