linux-kernel - Re: Querying the bios from booted linux kernel?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <477FDEC8.3020605@zytor.com>
Date:	Sat, 05 Jan 2008 11:47:20 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Matt Domsch <Matt_Domsch@...l.com>
CC:	Gene Heskett <gene.heskett@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Querying the bios from booted linux kernel?

Matt Domsch wrote:
> 
> parted and fdisk both write into the MBR signature space, so your
> disks should have unique MBR values in them.
> 

parted did so incorrectly, and had less than 20 bits of randomness.

fdisk only does so as of a very recent version (I put that in after I 
noticed a whole bunch of disks I had had zero identifiers.)

sfdisk doesn't at all, last I checked.

None check for collisions.

> I've given up trusting any BIOS to get EDD 3.0 device paths right,
> there are just too many broken implementations out there, and
> seemingly no real desire on the part of the component vendors to fix
> it.  MBR signatures work pretty well - Dell uses this method for every
> one of our factory installed Linux systems we ship, so I _know_ it works.

At least with a known distribution.  But yes, it really seems to be the 
most reliable method.

	-hpa


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