http://defect.opensolaris.org/bz/show_bug.cgi?id=11321
--- Comment #2 from Renee Danson Sommerfeld <renee.danson at sun.com> 2009-12-01 01:20:47 UTC --- (In reply to comment #1) [...] > Profile selection (and also wlan selection) requires > solaris.network.autoconf.refresh and solaris.network.autoconf.write > authorizations. Once the user has the write authorization, profiles can be > created or modified or destroyed. [...] > I think what we need is a new authorization that allows (sat > solaris.network.autoconf.select) which allows enabling/disabling of profiles. > If such an authorization exists, then the "autoconf user" would have the read, > select, refresh authorizations and the "autoconf admin" would have all read, > select, refresh, write. So the select auth would allow the bit of writing required to select/enable a profile, but not allow changing of other profile properties, which would still require the write auth. Correct? > We may also have to add a different authorization that > allows create/modify/destroy of the Known WLAN objects as the "autoconf user" > is expected to choose wlans and create wifi keys. It seems like a new solaris.network.autoconf.wifiadm authorization (alternative name suggestions welcome!) would work; that auth would be required (instead of autoconf.write) to create/modify known wlan objects. Is that sufficient? -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
