linux-kernel - Re: Firewire debugging tools

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: <1248968242.3624.28.camel@maxim-laptop>
Date:	Thu, 30 Jul 2009 18:37:22 +0300
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Jun Koi <junkoi2004@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Firewire debugging tools - firedump & fireproxy?

On Thu, 2009-07-30 at 11:43 +0200, Andi Kleen wrote:
> Jun Koi <junkoi2004@...il.com> writes:
> 
> > Hi,
> >
> > I am doing some debugging via firewire. I found some references to
> > some tools named firedump & fireproxy, made by Bernhard Kaindl,
> > supposed put at following addresses:
> >
> > ftp://ftp.suse.de/private/bk/firewire/tools/firedump-0.1.tar.bz2
> > ftp://ftp.suse.de/private/bk/firewire/tools/fireproxy-0.33.tar.bz2
> 
> I have a copy of Bernd's website on http://halobates.de/firewire
> 
> firescope is also on my servers (I did the original x86 version)
> 
> -Andi
> 
>  

Thanks a lot.
Don't know what to say about what I could do to help...
I could help to make this tool better, don't know how much time will
permit me, or at least I think that kgdbom can be merged almost as is
already.
As it stands from the source, it just creates a ring buffer in memory
for commands as if there were send over gdb. Dead simple it seems.
Thus, fireproxy could be reduced (if it isn't...) to simple "read string
from memory over firewire and hand over to gdb via tcp and vise versa.
This should give back all power kgdb has for free (currently fireproxy
states that only very basic support is implemented)

Could some of you put these tools on kernel.org?
Debugging over firewire seems to be the best of the best.

BTW, it is almost always possible to take over the CPU even without help
of kgdbom (if system got in state even it doesn't work)
Say CPU is in protected mode, and you know where the IDT lives.
You could program some device to trigger an IRQ (HPET seems to be the
best), set up the APIC to route it, and then trigger, and now the CPU
should enter the IRQ handler. (Of course this needs that firewire device
be able to access HPET and IOAPIC which are nowadays located on
southbridge)

And probably the only device that can't be debugged, is the firewire
driver itself that is standard compliant, and well tested...

Best regards,
	Maxim Levitsky

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