linux-kernel - Re: PC speaker

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: <Pine.LNX.4.64.0706152131450.32724@fbirervta.pbzchgretzou.qr>
Date:	Fri, 15 Jun 2007 21:34:52 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Phillip Susi <psusi@....rr.com>
cc:	"R.F. Burns" <burnsrf@...il.com>,
	Lee Revell <rlrevell@...-job.com>, linux-kernel@...r.kernel.org
Subject: Re: PC speaker


On Jun 15 2007 13:07, Phillip Susi wrote:
> R.F. Burns wrote:
>> However, over the past several weeks, the students have found more
>> creative ways to abuse the PC speaker (outside of the OS.)  The Powers
>> that Be are asking that the PC speakers be disabled completely.  With
>> the small number of techs we have, it would be very impractical to go
>> around to all systems and remove the PC speaker from each and every
>> computer case.
>
> Now I am curious; how are they getting the pc speaker to make any sound with
> the kernel module disabled?

ioperm(), inb(), and outb() from userspace. Needs root, though. Or 
/dev/port, with write. Which comes to the question how they gained root. 
Perhaps live cd? In which case, the OP should, as recommended in this 
thread already, deactivate choosing boot devices, if that's possible.

(Unfortunately, newer BIOSes with 'integrated bootmenu' with F8 or so, 
but I have not seen a way to deactivate _that_ menu.)



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