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>] [day] [month] [year] [list]
Date:	Tue, 24 Oct 2006 13:31:26 -0400
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	"Johannes Berg" <johannes@...solutions.net>
Cc:	netdev@...r.kernel.org, "Jiri Benc" <jbenc@...e.cz>,
	"John W. Linville" <linville@...driver.com>,
	"Jean Tourrilhes" <jt@....hp.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211

On 10/24/06, Johannes Berg <johannes@...solutions.net> wrote:
> Alright, here's more now that I can think clearly again :)
>
> > ISO 3166-1, as part of the ISO 3166 standard, provides codes for the names
> > of countries and dependent areas. It was first published in 1974 by
> > the International Organization for Standardization (ISO) and defines three
> > different codes for each area:
> >
> >     * ISO 3166-1 alpha-2, a two-letter system with many applications,
> >       most notably the Internet top-level domains (ccTLD) for countries.
> >     * ISO 3166-1 alpha-3, a three-letter system.
> >     * ISO 3166-1 numeric, a three-digit numerical system, which is
> >     identical to that defined by the United Nations Statistical Division.
> >
> > Although this would usually be only used in userspace IEEE-802.11d
> > has made use of ISO-3166-1 alpha 3. This mapping was added
> > to enhance stack support for IEEE-802.11d and 802.11 Regulatory
> > Domain control. ieee80211_regdomains makes use of this module
> > by creating a map of iso3166 alpha3 country code to stack
> > regulatory domain.
>
> But if 802.11d only requires alpha 3, why put all the other stuff into
> the kernel as well?

It would have been a half ass job for kernel iso3166-1 support, also
though -- I feel we should leave this as-is until we have an ironed
out userspace regulatory daemon. This would make regulatory
domain/802.11d/MLME daemon optional to introduce for distributions
until that part is done and distributions have happily adopted
something. Since its a complete iso3166-1 db I wondered if any other
modules would make use of it. An example of a similar db in the kernel
is for Native Language Support (NLS) for filesystems. If no modules
can make use of it the quicker this should be removed once we have a
userspace API ready.

CC'ing LKML to see if any other module can make use of this.

  Luis
-
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