Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756730AbZDFSow (ORCPT ); Mon, 6 Apr 2009 14:44:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753918AbZDFSok (ORCPT ); Mon, 6 Apr 2009 14:44:40 -0400 Received: from mail.vyatta.com ([76.74.103.46]:48908 "EHLO mail.vyatta.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752246AbZDFSoj (ORCPT ); Mon, 6 Apr 2009 14:44:39 -0400 Date: Mon, 6 Apr 2009 11:44:32 -0700 From: Stephen Hemminger To: Jeff Garzik Cc: Robin Getz , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Peterson , Matt Mackall , David Miller Subject: Re: IRQF_SAMPLE_RANDOM question... Message-ID: <20090406114432.3a554eba@nehalam> In-Reply-To: <49DA4C85.5090806@garzik.org> References: <200904061430.26276.rgetz@blackfin.uclinux.org> <49DA4C85.5090806@garzik.org> Organization: Vyatta X-Mailer: Claws Mail 3.6.1 (GTK+ 2.16.0; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2488 Lines: 59 On Mon, 06 Apr 2009 14:40:05 -0400 Jeff Garzik wrote: > Robin Getz wrote: > > Although there was some discussion > > http://thread.gmane.org/gmane.linux.kernel/680723 > > > > about removing IRQF_SAMPLE_RANDOM from the remaining network drivers in May of > > 2008, but they still appears to be there in 2.6.29. > > > > drivers/net/ibmlana.c > > drivers/net/macb.c > > drivers/net/3c523.c > > drivers/net/3c527.c > > drivers/net/netxen/netxen_nic_main.c > > drivers/net/cris/eth_v10.c > > drivers/net/xen-netfront.c > > drivers/net/atlx/atl1.c > > drivers/net/qla3xxx.c > > drivers/net/tg3.c > > drivers/net/niu.c > > > > So what is the plan? If I send a patch to add IRQF_SAMPLE_RANDOM to others > > (like the Blackfin) networking drivers - will it get rejected? > > > > We have lots of embedded headless systems (no keyboard/mouse, no soundcard, no > > video) systems with *no* sources of entropy - and people using SSL. > > > > I didn't really find any docs which describe what should have > > IRQF_SAMPLE_RANDOM on it or not. I did find Matt Mackall describing it as: > >> We currently assume that IRQF_SAMPLE_RANDOM means 'this is a completely > >> trusted unobservable entropy source' which is obviously wrong for > >> network devices but is right for some other classes of device. > > > > Currently - I see most things I see using IRQF_SAMPLE_RANDOM would also fail > > the "completely unobservable" test. Other than the TRNG that are inside the > > CPU - what does pass? > > IMO it's not observation but rather that a remote host is essentially > your source of entropy -- which means your source of entropy is > potentially controllable or influenced by an attacker. > > Furthermore, with hardware interrupt mitigation, non-trivial traffic > levels can imply that interrupts are delivered with timer-based > regularity. This, too, may clearly be influenced by a remote attacker. > > Thus I think IRQF_SAMPLE_RANDOM should be banned from network drivers... > but that is not a universal opinion. > > Jeff The real problem one is xen-netfront. Because 1) it is least random, the attacker might be another VM 2) the VM is most in need of random samples because it doesn't have real hardware. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/