netdev - Re: rfkill vs. interface up

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: <1242921924.4212.11.camel@johannes.local>
Date:	Thu, 21 May 2009 18:05:24 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Dan Williams <dcbw@...hat.com>
Cc:	linux-wireless <linux-wireless@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: Re: rfkill vs. interface up

On Thu, 2009-05-21 at 11:39 -0400, Dan Williams wrote:

> That proposal sounds fine to me from a userspace perspective.  Sane
> implementations don't assume the interface is IFF_UP when they configure
> the device anyway (since it's not necessarily up at boot time or after
> hibernate for example), and since you need a reconfigure after rfkill,
> this seems reasonable.
> 
> You wouldn't have to give up on txpower either, you could simply map
> 'txpower off' to SW-rfkill, and 'txpower on' to un-SW-rfkill, where of
> course the interface would be !IFF_UP after 'txpower on' just like
> flipping the killswitch would.

Yeah, good point, that sounds better than having to give up on it -- the
key though is that we can't recover IFF_UP state when that happens; if
that's ok this should be fairly simple.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)