linux-kernel - Re: 2.6.23-rc1: no setup signature found...

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: <46AC9B28.6060906@zytor.com>
Date:	Sun, 29 Jul 2007 06:50:32 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	bbpetkov@...oo.de
CC:	Xudong Guan <xudong.guan@...il.com>, linux-kernel@...r.kernel.org,
	Chuck Ebbert <cebbert@...hat.com>
Subject: Re: 2.6.23-rc1: no setup signature found...

Borislav Petkov wrote:
> 
> Right, this was too easy to be true. I now did:
> 
> qemu -hda /dev/hda -snapshot
> 
> and booted from the hd using the installed grub and the same kernel and it
> _didn't_ boot showing again "no setup signature found... "
> 

Okay, so it's an algorithmic problem.  This is quite important to know.

Is /boot a separate partition on your disk by any chance?  Either way, 
this means we can use qemu to debug this, which will make it a lot easier.

This is what I'd like you to do next:

- run qemu in one window with the -S -s options.
- in another window, do:

	gdb
	target remote localhost:1234
	set architecture i8086
	disp/i ($cs << 4)+$eip
	br *0x10200
	br *0x20200
	br *0x30200
	br *0x40200
	br *0x50200
	br *0x60200
	br *0x70200
	br *0x80200
	br *0x90200
	c

	# ... hopefully you're now stopped at a jump instruction
	p/x $ds
	
	# Hopefully this is showing, say, 0x9000 if you're stopped
	# at 0x90200

	# Where X is the first digit of the address stopped at:
	dump memory setup.dump 0xX0000 0xX8000


Please send me setup.dump plus your vmlinuz file.

Thanks,

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