linux-kernel - Re: [stable] Linux 2.6.25.10

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Jul 2008 21:38:25 -0300
From:	Tiago Assumpcao <tiago@...umpcao.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	pageexec@...email.hu, Greg KH <greg@...ah.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [stable] Linux 2.6.25.10

Linus Torvalds wrote:
> 
> On Tue, 15 Jul 2008, Tiago Assumpcao wrote:
>> However, as I previously explained [http://lkml.org/lkml/2008/7/15/654],
>> security issues are identified and communicated through what can be a long and
>> complicated (due to DNAs, etc.) process. If it culminates at implementation,
>> without proper information forwarding from the development team, it will never
>> reach the "upper layers" -- vendors, distributors, end users, et al.
> 
> Umm. That shouldn't be our worry.

Yeah, at this point, it is clear to the world. No needs for repeated 
wording ;)

> If others had a long and involved (and broken) process, they should be the ones that track the fixes too. We 
> weren't involved, we didn't see that, we simply _cannot_ care.

You weren't involved? Hold on, aren't you the developers, thence, those 
who commit mistakes, a.k.a the bug inducing point?

> 
>> Therefore, yes, it is of major importance that you people, too, buy the
>> problem and support the process as a whole. Otherwise... well, otherwise,
>> we're back to where we started, 20 years ago. Good luck Linux users.
> 
> Umm. What was wrong with 20 years ago exactly?

What was wrong for the computer theoretic people about 100 years ago? 
Lack of development? Not sure. Perhaps the same that existed for 
information security 20 years ago. Just perhaps.

I apologize for assuming you hold such information, anyway.

> 
> Are you talking about all the wonderful work that the DNS people did for 
> that new bug, and how they are heroes for synchronizing a fix and keeping 
> it all under wraps?
> 
> And isn't that the same bug that djb talked about and fixed in djbdns from 
> the start? Which he did about ten YEARS ago?

Are you trying to justify your irresponsibly indulgent act towards the 
operating system that my mother is likely to use with one alone 
exception? Because it rains umbrellas are a waste of time?

> 
> Excuse me for not exactly being a huge fan of "security lists" and best 
> practices. They seem to be _entirely_ be based on PR and how much you can 
> talk up a specific bug. No thank you,
> 
> 			Linus

Personally, I, too, have a major disgust for most crap seen in the so 
called info-sec world. I hand you my agreement on this one.
Except, it changes in nothing your responsibilities.

Take good care,
--t



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/