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:	Mon, 3 Nov 2008 17:06:17 -0200
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Alan Jenkins <alan-jenkins@...fmail.co.uk>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-wireless@...r.kernel.org
Subject: Re: rfkill, stupid question #6

On Mon, 03 Nov 2008, Alan Jenkins wrote:
> I have one more question.  I read that if a STATE_SOFT_BLOCKED request
> is made when the hardware is in STATE_HARD_BLOCKED, the rfkill driver is
> expected to "double block".

If it can do so, yes.  It makes for marginally better use interaction.

> If the hard block is later cleared, the driver is expected to call
> rfkill_force_state(SOFT_BLOCKED).  The SOFT_BLOCKED state can then be
> cleared as normal.

Exactly.

> But if there is an UNBLOCK request in the double-blocked state, the
> rfkill core will reject it and preserve the  double-blocked state.  Is
> this intended, or a known issue?

It is intended.  The user wants to unblock the radio (not "prepare it to
unblock when I release the hardware rfkill line by doing something else"),
so we have to error it out.

And, frankly, I don't very much like the idea of the core returning a
-EPERM and yet having done a call toggle_radio(UNBLOCK).   Not to mention
it is yet another border condition for the hook API.

So, if something took the pains to cause a double block, we require
explicit unblocking AFTER the hardware rfkill lines are released (i.e. the
device goes from HARD to SOFT blocked).

BUT I don't feel strongly about it, so if someone wants to change that, I
won't stand in the way.

> Wouldn't it be simpler to use a bitmask so that the rfkill core can at
> least represent this double-blocked state?  I guess the problem would be
> how to shoehorn it into the sysfs interface.

The core doesn't care, and doesn't have to in order to implement such a
thing.  The drivers track it separately.

The two problems is that it can be REALLY confusing for the end user, and
that it requires a ABI change.  I don't know if it is worth it, I just know
I am not going to be the one doing it :-)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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