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: <46AE4E29.7060402@zytor.com>
Date:	Mon, 30 Jul 2007 13:46:33 -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:
> 
> Hi,
> 
> i decided to do some cheating :) and skipped the breakpoint where it used to
> stop (0x40200). (by the way, hitting 'c' wouldn't continue at all and keep
> executing the same instruction over and over again). This time it seems it behaves as expected:
> 

Uhm, it looks to me that you ran qemu with the -kernel option again (I 
can tell because the dump exhibits a few bugs that are characteristic of 
the qemu loader.)  This makes qemu itself load the kernel and not rely 
on the boot loader that's on your bootloader.

I was expecting you to run "qemu -S -s -hda /dev/hda -snapshot", which 
you previously said when run (without the -S -s) options reproduced the 
problem.

After taking the dump, please do:

	delete
	c

... to verify the problem is reproduced.

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/