Thursday May 27, 2010
Tuesday May 25, 2010
By Brian Leonard on May 25, 2010
Of all the components of Solaris' Role Based Access Control (RBAC), roles are the easiest the implement. When I explain the concept of roles to people, they immediately get it.
OpenSolaris comes with a couple of roles pre-configured, most notably root.
This has led to some frustration for newcomers to OpenSolaris as they
don't understand why they can't log into their system as root.
But, as there is most likely no person in your organization named 'root', why do you wnat a user account on your system for a person that doesn't exist? Who is this root user and who's accountable for what they do on the system? Over time the password for the root user account always seems to proliferate. The principle of least privilege, another RBAC concept that I'm not addressing here, is meant to limit the need to hand out root access, but even in the absence of that, wouldn't it be nice to know who's doing what as root on your system?[Read More]
Friday Dec 05, 2008
- Multi-CPU Binding (MCB)
- Which Oracle Solaris Virtualization?
- VXLAN in Solaris 11.2
- DTrace improvements in Oracle Solaris 11.2
- Solaris-specific Providers for Puppet
- OpenSSL on Oracle Solaris 11.2
- Puppet Configuration in Solaris
- New in SMF Documentation for Oracle Solaris 11.2
- New in IPS Documentation for Oracle Solaris 11.2
- The Technical Details: April 29 Oracle Solaris 11.2 Launch