linux-kernel - Re: Bug 10173 / Bluetooth on Toshiba & Compal laptops

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: <5a670e0fe13a5f433ef207efefd71ca2@localhost>
Date:	Mon, 15 Dec 2008 17:47:25 -0500
From:	Philip Langdale <philipl@...rt.org>
To:	"Robert M. Albrecht" <mail@...al.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Bug 10173 / Bluetooth on Toshiba & Compal laptops

On Mon, 15 Dec 2008 23:34:52 +0100, "Robert M. Albrecht" <mail@...al.de>
wrote:
> Hi Phil,
> 
> anything I can do ? Providing some logs or granting ssh access to the 
> machine to have a look ?

If necessary, that would be useful. However, the first question to ask is
actually
related to my possibility C) - which I'm now re-evaluating as much more
likely.

If you don't load the 'rfkill-input' module, then there is no policy
applied to
killswitch handling. The core driver puts the device in the SOFT_BLOCKED
state
when the de-assert the hardware switch. rfkill-input contains the policy
that
decides to go one step further and re-enable the device. This module has no
hardware dependencies so it is not automatically loaded - you must do it
explicitly yourself.

If that's not your problem, then we'll have to dig deeper.

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