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]
Date:	Sat, 11 Jul 2009 21:59:11 +0200
From:	Norbert Preining <preining@...ic.at>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	linux-kernel@...r.kernel.org,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: rfkill rework in 2.6.31-rc, hal/dbus access changes?

Hi Marcel, hi all,

On Sa, 11 Jul 2009, Marcel Holtmann wrote:
> > - formerly writing 0 or 1 to /sys/class/rfkill/rfkillN/state worked, now
> >   it returns access denied.
> 
> actually Johannes sent a patch to fix this. It will still return an
> error if the RFKILL switch is hard-blocked btw.

I found that and have just now rebooted into -rc2 with this patch
applied, and yes, it works again.

> > - access via Hal/Dbus (what I am doing) stopped working, too
> 
> Not the first time HAL broke in this area, because its RFKILL support is
> a bunch of hacked up scripts. Send a patch to the HAL mailing list.

Indeed *with* Johannes' patch also HAL/Dbus access works again, so I
don't have to dig into that again. Probably at the end of the line both
hal and sys access to the state file ended up in the same dead end which
was fixed by the patch.

So thanks, Johannes, all fine now.

> You could just go ahead and work on fixing HAL.

That is far out of my abilities, I was happy to hack a gnome applet in
python using hal/dbus, that fine.

> The /dev/rfkill interface is the only way to get a proper interface with

But reading from that file directly is not a piece of cake, at least I
haven't seen any specification of the format. I have downloaded the
rfkill user space utility and will try to use that one instead, but that
makes it more difficult due to access permission gamble.

So, /dev/rfkill and the rfkill user mode program is the way to go?

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@...ic.at>        Vienna University of Technology
Debian Developer <preining@...ian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
FROLESWORTH (n.)
Measure. The minimum time it is necessary to spend frowning in deep
concentration at each picture in an art gallery in order that everyone
else doesn't think you've a complete moron.
			--- Douglas Adams, The Meaning of Liff
--
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