linux-kernel - Re: The state of linux security

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]

Message-ID: <alpine.DEB.1.10.0807160928150.17859@asgard.lang.hm>
Date:	Wed, 16 Jul 2008 09:38:04 -0700 (PDT)
From:	david@...g.hm
To:	Cheradenine Zakalwe <sc.contact@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: The state of linux security

On Wed, 16 Jul 2008, Cheradenine Zakalwe wrote:

> If it turns out that the current development model has produced too
> many security problems then the development model must change. I'd
> like to think that the integrity of most peoples systems is more
> important than some micro benchmark improvement because of some
> complex scheduler change.  That's not to say the latter isn't
> important, just that more time and effort needs to be put into making
> sure that the changes don't affect users in potentially disasterous
> ways.

how can you tell for sure if a bug has security implications or not?

the argument can be made that just about any bug can be a security bug

frequently the security implications of a bug are not known at the time 
it's fixed, but are discovered later. how do you expect to have this in 
the announcements?

if you only upgrade when there is a 'security bug' announcement you will 
miss a lot of important upgrades.

as Linus stated, there's nothing preventing anyone who thinks that he's 
not doing an appropriate job from doing the research on the security 
implications of everything and doing their own announcements or just 
maintaining their own tree.

David Lang
--
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/