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-next>] [day] [month] [year] [list]
Message-ID: <CAB=NE6W4Q2ngB6CF8pG=OV6=q+9CTcwA6UGhdgS+OCT++N2GJA@mail.gmail.com>
Date:	Thu, 9 Apr 2015 17:57:44 -0700
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:	linux-wireless <linux-wireless@...r.kernel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Kees Cook <kees@...flux.net>,
	Ming Lei <ming.lei@...onical.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Johannes Berg <johannes@...solutions.net>,
	Seth Forshee <seth.forshee@...onical.com>,
	"Luis R. Rodriguez" <mcgrof@...e.com>,
	netfilter-devel@...r.kernel.org
Subject: Looking for extensible kernel database format

Hey folks,

next week I'd like to address replacing the need for CRDA [0] as a
udev helper with in-kernel functionality  There's a few motivations
for this but a good one is that the kernel already has now
cryptographic support to verify the integrity of the regulatory
database, just as it has support for verifying the integrity of
modules / firmware. We'd use something like:

request_file(file_reqs)

Where the file_reqs provides the requirements, including cryptographic
requirements, and I suspect we'd use LSM to vet for the cryptographic
needs of the file.

Now other than this step CRDA currently *reads* a database and today
we have our own format. If we want to extend this though we will have
to issue a new regdb format and old kernels might not be compatible
with the new format. This is a typical database problem and I'm hoping
we are not the first to deal with this. What *extensible* kernel
database format are there already, are they generic already? I'd
prefer something already using netlink.

Any recommendations?

[0] https://wireless.wiki.kernel.org/en/developers/regulatory/crda

  Luis
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ