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: <20060730163203.GA31495@srcf.ucam.org>
Date:	Sun, 30 Jul 2006 17:32:03 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Jan Dittmer <jdi@....org>
Cc:	Theodore Tso <tytso@....edu>, Kasper Sandberg <lkml@...anurb.dk>,
	Pavel Machek <pavel@...e.cz>,
	Jirka Lenost Benc <jbenc@...e.cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	ipw2100-admin@...ux.intel.com
Subject: Re: ipw3945 status

On Sun, Jul 30, 2006 at 06:25:34PM +0200, Jan Dittmer wrote:

> So if this is done, there should be a clearly abstracted interface
> for such a daemon. I don't see what the daemon is doing more than
> echo 1 4 7 8 > /sys/.../allowed_channels and a control circuit for
> tx/rx power.

The daemon sets the list of acceptable channels, the transmission powers 
for each of them and modifies this based on things like the temperature.

Oh, yes, and it writes 802.11 scan frames that get passed straight to 
the firmware and broadcast. Insane crack. For reasons I don't as yet 
understand, various received frames also get passed back up to the 
daemon. I probably really don't want to know why.
-- 
Matthew Garrett | mjg59@...f.ucam.org
-
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