en Copyright 2015 Java http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/secmodel/files.secmodel#926571dfa7ef284889680baba2775046b1ad67ea Implement the register/deregister/evaluation API for secmodel(9). Itallows registration of callbacks that can be used later forcross-secmodel "safe" communication.When a secmodel wishes to know a property maintained by anothersecmodel, it has to submit a request to it so the other secmodel canproceed to evaluating the request. This is done through thesecmodel_eval(9) call; example: bool isroot; error = secmodel_eval("org.netbsd.secmodel.suser", "is-root", cred, &isroot); if (error == 0 && !isroot) result = KAUTH_RESULT_DENY;This one asks the suser module if the credentials are assumed to be rootwhen evaluated by suser module. If the module is present, it willrespond. If absent, the call will return an error.Args and command are arbitrarily defined; it's up to the secmodel(9) todocument what it expects.Typical example is securelevel testing: when someone wants to knowwhether securelevel is raised above a certain level or not, the callerhas to request this property to the secmodel_securelevel(9) module.Given that securelevel module may be absent from system's context (thusmaking access to the global "securelevel" variable impossible orunsafe), this API can cope with this absence and return an error.We are using secmodel_eval(9) to implement a secmodel_extensions(9)module, which plugs with the bsd44, suser and securelevel secmodelsto provide the logic behind curtain, usermount and user_set_cpu_affinitymodes, without adding hooks to traditional secmodels. This solves areal issue with the current secmodel(9) code, as usermount oruser_set_cpu_affinity are not really tied to secmodel_suser(9).The secmodel_eval(9) is also used to restrict security.models settingswhen securelevel is above 0, through the "is-securelevel-above"evaluation:- curtain can be enabled any time, but cannot be disabled ifsecurelevel is above 0.- usermount/user_set_cpu_affinity can be disabled any time, but cannotbe enabled if securelevel is above 0.Regarding sysctl(7) entries:curtain and usermount are now found under security.models.extensionstree. The security.curtain and vfs.generic.usermount are stillaccessible for backwards compat.Documentation is incoming, I am proof-reading my writings.Written by elad@, reviewed and tested (anita test + interact for rightstests) by me. ok elad@.See alsohttp://mail-index.netbsd.org/tech-security/2011/11/29/msg000422.htmlXXX might consider va0 mapping too.XXX Having a secmodel(9) specific printf (like aprint_*) for reportingsecmodel(9) errors might be a good idea, but I am not sure on howto design such a function right now. List of files: /netbsd-src/sys/secmodel/files.secmodel Sun, 04 Dec 2011 19:24:58 +0000 jym <jym@NetBSD.org> http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/secmodel/files.secmodel#53ca19a3b3534aed3244e88a0a4af79fef857ad0 First part of secmodel cleanup and other misc. changes: - Separate the suser part of the bsd44 secmodel into its own secmodel and directory, pending even more cleanups. For revision history purposes, the original location of the files was src/sys/secmodel/bsd44/secmodel_bsd44_suser.c src/sys/secmodel/bsd44/suser.h - Add a man-page for secmodel_suser(9) and update the one for secmodel_bsd44(9). - Add a "secmodel" module class and use it. Userland program and documentation updated. - Manage secmodel count (nsecmodels) through the module framework. This eliminates the need for secmodel_{,de}register() calls in secmodel code. - Prepare for secmodel modularization by adding relevant module bits. The secmodels don't allow auto unload. The bsd44 secmodel depends on the suser and securelevel secmodels. The overlay secmodel depends on the bsd44 secmodel. As the module class is only cosmetic, and to prevent ambiguity, the bsd44 and overlay secmodels are prefixed with "secmodel_". - Adapt the overlay secmodel to recent changes (mainly vnode scope). - Stop using link-sets for the sysctl node(s) creation. - Keep sysctl variables under nodes of their relevant secmodels. In other words, don't create duplicates for the suser/securelevel secmodels under the bsd44 secmodel, as the latter is merely used for "grouping". - For the suser and securelevel secmodels, "advertise presence" in relevant sysctl nodes (sysctl.security.models.{suser,securelevel}). - Get rid of the LKM preprocessor stuff. - As secmodels are now modules, there's no need for an explicit call to secmodel_start(); it's handled by the module framework. That said, the module framework was adjusted to properly load secmodels early during system startup. - Adapt rump to changes: Instead of using empty stubs for securelevel, simply use the suser secmodel. Also replace secmodel_start() with a call to secmodel_suser_start(). - 5.99.20.Testing was done on i386 ("release" build). Spearated module_init()changes were tested on sparc and sparc64 as well by martin@ (thanks!).Mailing list reference: http://mail-index.netbsd.org/tech-kern/2009/09/25/msg006135.html List of files: /netbsd-src/sys/secmodel/files.secmodel Fri, 02 Oct 2009 18:50:12 +0000 elad <elad@NetBSD.org> http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/secmodel/files.secmodel#3ab4ce47390fba8ab2d73f4d5ae27e1c20b09298 Add support for multi-position electro-mechanical keylocks. An exampledriver, gpiolock(4), is provided as an example how to interface real hardware.A new securemodel, securemodel_keylock, is provided to show how this canbe used to tie keylocks to overall system security. This is experimentalcode. The diff has been on tech-kern for several weeks.Reviewed by many, kauth(9) integration reviewed by Elad Efrat; approved bytonnerre@ and tron@. Thanks to everyone who provided feedback. List of files: /netbsd-src/sys/secmodel/files.secmodel Fri, 14 Aug 2009 21:17:21 +0000 mbalmer <mbalmer@NetBSD.org> http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/secmodel/files.secmodel#6887492c261e6d27ac6fa6294fb8552ffcfd0c49 Make securelevel a "secmodel" of its own.While it's true that it's part of the traditional 4.4BSD security model,there may come a time where a different "primary" security model used forfine-grained privileges (ie., splitting root's responsibilities to variousprivileges that can be assigned) may want to still have a securelevelsetting.Idea from Daniel Carosone: http://mail-index.netbsd.org/tech-security/2006/08/25/0001.htmlThe location of the removed files, for reference, was: src/secmodel/bsd44/secmodel_bsd44_securelevel.c src/secmodel/bsd44/securelevel.h List of files: /netbsd-src/sys/secmodel/files.secmodel Wed, 21 Nov 2007 22:49:05 +0000 elad <elad@NetBSD.org> http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/secmodel/files.secmodel#5f7169ccb1d349e91f3fbefef9c51d04dc8a863e First take at security model abstraction.- Add a few scopes to the kernel: system, network, and machdep.- Add a few more actions/sub-actions (requests), and start using them as opposed to the KAUTH_GENERIC_ISSUSER place-holders.- Introduce a basic set of listeners that implement our "traditional" security model, called "bsd44". This is the default (and only) model we have at the moment.- Update all relevant documentation.- Add some code and docs to help folks who want to actually use this stuff: * There's a sample overlay model, sitting on-top of "bsd44", for fast experimenting with tweaking just a subset of an existing model. This is pretty cool because it's *really* straightforward to do stuff you had to use ugly hacks for until now... * And of course, documentation describing how to do the above for quick reference, including code samples.All of these changes were tested for regressions using a Python-basedtestsuite that will be (I hope) available soon via pkgsrc. Informationabout the tests, and how to write new ones, can be found on: http://kauth.linbsd.org/kauthwikiNOTE FOR DEVELOPERS: *PLEASE* don't add any code that does any of thefollowing: - Uses a KAUTH_GENERIC_ISSUSER kauth(9) request, - Checks 'securelevel' directly, - Checks a uid/gid directly.(or if you feel you have to, contact me first)This is still work in progress; It's far from being done, but now it'llbe a lot easier.Relevant mailing list threads:http://mail-index.netbsd.org/tech-security/2006/01/25/0011.htmlhttp://mail-index.netbsd.org/tech-security/2006/03/24/0001.htmlhttp://mail-index.netbsd.org/tech-security/2006/04/18/0000.htmlhttp://mail-index.netbsd.org/tech-security/2006/05/15/0000.htmlhttp://mail-index.netbsd.org/tech-security/2006/08/01/0000.htmlhttp://mail-index.netbsd.org/tech-security/2006/08/25/0000.htmlMany thanks to YAMAMOTO Takashi, Matt Thomas, and Christos Zoulas for helpstablizing kauth(9).Full credit for the regression tests, making sure these changes didn't breakanything, goes to Matt Fleming and Jaime Fournier.Happy birthday Randi! :) List of files: /netbsd-src/sys/secmodel/files.secmodel Fri, 08 Sep 2006 20:58:56 +0000 elad <elad@NetBSD.org>