- Alexander Leidinger - http://www.leidinger.net/blog -

Rants about JASS (Sol­aris Se­cur­ity Toolkit)

Re­cently I switched to a new cli­ent where the Sol­aris [1] Se­cur­ity [2] Toolkit (JASS) is ex­tens­ively used. I am now in the pro­cess of up­dat­ing some things, among them are JET and JASS. As part of this work I ree­valu­ate the local JASS modi­fic­a­tions. Pre­vi­ously a cus­tom JASS pack­age was used, but in case JASS is up­dated by Or­acle [3] at some point in time (and an up­date is really needed, see be­low), this would need some amount of work to find out the dif­fer­ences and to for­ward port them to the new ver­sion. If everything is well doc­u­mented, this should not be hard to do, but the per­son do­ing the work also needs to find the up-to-date docs.

To make it more easy I de­cided to change this. I now in­stall the of­fi­cial JASS pack­age via JET to­gether with the latest patch for it, and then let JET copy our modi­fic­a­tions over the in­stalled pack­age. In­stead of modi­fy­ing ex­ist­ing drivers, I cre­ated our own drivers with a ref­er­ence to the driver which served as a base.

While do­ing this I en­countered sev­eral short­com­ings of JASS on Sol­aris [4] 10.

There are sev­eral FS based checks which do not make sense to do for the FS of zones in a global zone (at least not the way I use JASS, so maybe a con­fig­ur­able way of chan­ging the be­ha­vior should serve for every­one). If zones are in­stalled in /zones, you do not need to check for files without valid UIDs (you surely find a lot of files, as the users are defined in­side the zones and not in the global zone) or sim­ilar things (even not for world writ­able files, as the zones are in­stalled in a root-access-only sub­tree and in­side the zones there may be other se­cur­ity con­straints con­figured in­side JASS, read: it is the re­spons­ib­il­ity of JASS in­side the zone to do this). An easy solu­tion would be to ex­clude those FS which con­tain zones (and as we only have one sub­tree, I just hard­coded this in sev­eral scripts [5]).

I also miss the pos­sib­il­ity (maybe I over­looked a simple way) for the ssh check to limit the Al­low­Root­Lo­gin to spe­cific hosts. JASS only checks yes or no, but can not limit it to spe­cific hosts (e.g. via “Match [6] IP/hostname”). Of­ten you do not need to per­mit root-logins (RBAC/sudo/…), but some­times it is the only way to handle a par­tic­u­lar edge-case (or to speed up an ac­tion dra­mat­ic­ally), and in such cases you do not want to al­low root-logins more than ne­ces­sary.

[12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] [56]Share/Save [57]
2 Comments (Open | Close)

2 Comments To "Rants about JASS (Sol­aris Se­cur­ity Toolkit)"

#1 Comment By Jason Callaway On August 11, 2011 @ 14:50


You bring up some good points. If you have made any cus­tom­iz­a­tions to the JASS code base, feel free to send them over, and I’ll see if we can in­teg­rate them into the next ver­sion. FYI, SUN­W­jass 4.2.2 is avail­able here ( [58]). If you get a chance to test it, please let me know how it goes.


#2 Comment By netchild On August 11, 2011 @ 16:34

I will send you some­thing I can share later (maybe to­mor­row). For things I can not share, I will give a de­scrip­tion.