linux-kernel - Re: [PATCH 1/1 v2 ] ipmi: Setting OS name as Linux in BMC

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: <4FEDBB3C.7080105@acm.org>
Date:	Fri, 29 Jun 2012 09:27:08 -0500
From:	Corey Minyard <tcminyard@...il.com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	Andi Kleen <andi@...stfloor.org>, Srinivas_G_Gowda@...l.com,
	tcminyard@...il.com, linux-kernel@...r.kernel.org,
	"openipmi-developer@...ts.sourceforge.net" 
	<openipmi-developer@...ts.sourceforge.net>, jharg93@...il.com
Subject: Re: [PATCH 1/1 v2 ] ipmi: Setting OS name as Linux in BMC

On 06/29/2012 07:30 AM, Matthew Garrett wrote:
> On Thu, Jun 28, 2012 at 05:01:54PM -0700, Andi Kleen wrote:
>> Not sure that's all that useful. I can just see BMC's making the ACPI
>> mistake of trying to work around specific issues, by checking for
>> Linux.

I'm not sure I see that happening, but I suppose you never know.

>>
>> But since there are so many different Linux that will never work
>> because "Linux" does not describe a fixed release or code base.
>>
>> Probably dangerous.
> Agreed. Linux doesn't make interface guarantees to hardware, and where
> we've implied that we do it's ended up breaking things.
>

This is not really about making interface guarantees to hardware. This 
is more of a management discovery thing, so that system management 
software talking to the BMC can know what is running on the target.  
Something where management software can say "Hey, why is Linux running 
on that box? It's supposed to be BSD." or "That box has booted Linux but 
hasn't started its maintenance software". According to the spec, the 
information is supposed to be cleared if the system powers down or resets.

It seems to me that it's better to directly query what is running on the 
target to know what is running on it, but perhaps that's a security 
problem waiting to happen.  And perhaps it's better to have a small 
program set this at startup, since this operation will currently fail on 
the majority of systems out there.

-corey
--
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/