Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32Lyvy__nHrg for ; Thu, 24 Oct 2013 14:30:22 +0200 (CEST) Received: from v6.tansi.org (unknown [87.118.116.4]) by mail.saout.de (Postfix) with ESMTP for ; Thu, 24 Oct 2013 14:30:22 +0200 (CEST) Received: from gatewagner.dyndns.org (77-57-44-254.dclient.hispeed.ch [77.57.44.254]) by v6.tansi.org (Postfix) with ESMTPA id 6C8BB20DC175 for ; Thu, 24 Oct 2013 14:30:22 +0200 (CEST) Date: Thu, 24 Oct 2013 14:30:22 +0200 From: Arno Wagner Message-ID: <20131024123021.GA8187@tansi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [dm-crypt] Research on practical software crypto random number generation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de As this topic crops up on the list frequently (and deservedly), here is a current reference by Nadia Heninger et. al. that discusses this problem in the context of generating SSH/SSL keys and certificates. This paper has a nicely strong experimental section that validates the analysis, quite in contrast to a lot of other work in the field. This was in a Blog article some time ago, but they now have a short and a long paper linked here: https://factorable.net/paper.html I can particularly recommend reading Sections 4.1, 4.2 and 5.1 of the long paper. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. --Tony Hoare