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-next>] [day] [month] [year] [list]
Message-ID: <20070822094915.41afa2af@lore.lcone>
Date:	Wed, 22 Aug 2007 09:49:15 +0200
From:	RafaƂ Maj <forlist@...core.com>
To:	linux-kernel@...r.kernel.org
Subject: Calling BIOS interrupt from kernel (and debugging / reverse
 engeneering)


Hello,
I know it is not good to call BIOS interrupt from Linux (kernel nor
userspace) and we should use I/O ports instead;

But, is it at all doable? To call a BIOS interrupt from Linux kernel?

If so then how to?

In example, say we have not documented device returning data in AL
after call to interrupt 0x15 with AX=0x1234 for example; And we want to
use this BIOS interrupt and then printk() returned value in AL.

AFAIK vm86() is one step to do it, but its hard to find good complete
example at least for me.

Btw, is it possible to reverse engineering such a BIOS call? Besides
using some hardware-debugger of bus etc.

Thanks










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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ