Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756232AbYGTBOR (ORCPT ); Sat, 19 Jul 2008 21:14:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754814AbYGTBOE (ORCPT ); Sat, 19 Jul 2008 21:14:04 -0400 Received: from quechua.inka.de ([193.197.184.2]:36382 "EHLO mail.inka.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754788AbYGTBOE (ORCPT ); Sat, 19 Jul 2008 21:14:04 -0400 From: Bernd Eckenfels To: linux-kernel@vger.kernel.org Subject: Re: [stable] Linux 2.6.25.10 Organization: Private Site running Debian GNU/Linux In-Reply-To: <487D0564.7070606@assumpcao.org> X-Newsgroups: ka.lists.linux.kernel User-Agent: tin/1.7.8-20050315 ("Scalpay") (UNIX) (Linux/2.6.13.4 (i686)) Message-Id: Date: Sun, 20 Jul 2008 03:13:59 +0200 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1157 Lines: 26 In article <487D0564.7070606@assumpcao.org> you wrote: > Opinions apart, what really matters: we have an ultimate declaration > about Linus' tree -- we may forget the pre-official (?) announcement > [Documentation/SecurityBugs] and know that someone else must, > eventually, classify and inform the world about security bugs existent > in their software. The Security Comunity as a whole (especially the commercial service offices who gat paied to make up new security leaks) is very good in finding, tracking and classifying bugs. This together with the distributors works very well for Linux users. What are you missing? > From our consumer side, every time an issue of this nature is found, > let's pray for some intermediate, gray, angel to send us an "warning" > message. Well, since most often the developers rely on the same source to be notified about it, its not really a problem. Gruss Bernd -- 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/