Configd RBAC- now can't get to root

My story is sad (but stupid). I am trying to harden

a Sun-Fire V240 in prep for a security accreditation

next week. I just finished writing the script I planned to run on the other boxes. The government security manual wants me to use RBAC; its been a long time since I studiedRBAC. But I followed the guidance in the book. So i changed my user_attr from:

root::::type=normal;auths=solaris.*,solaris.grant;profiles=All

to

root::::type=role;auths=solaris.*,solaris.grant;profiles=All

There are no other entries in user_attr.

I booted.

I logged in as the normal sysadmin account (ingest) and tried to su and it does not work. I get " Roles

can only be assumed by authorized users".

I can't su, or boot to Single User Mode. I did copy

the user_attr to user_attr.orig before I changed it but it is owned by root so that's no help.

I'm afraid that I am looking at a reload. And of course, the script is in a 400 perm directory.

Does anybody have any ideas how I can either

copy the original user_attr or add the ingest user

without having access to root or su.

[1163 byte] By [card2642] at [2007-11-25 23:40:35]
# 1

> But I followed the

> guidance in the book. So i changed my user_attr

> from:

>

> root::::type=normal;auths=solaris.*,solaris.grant;prof

> iles=All

>

> to

>

> root::::type=role;auths=solaris.*,solaris.grant;profil

> es=All

That is a really bad thing to do. You really do not want to mess with your root account like this. This can even render other services totally useless. Still, this is also the reason why its smart to keep an account around and give it the "Primary Administrator" profile.

> I can't su, or boot to Single User Mode. I did copy

> the user_attr to user_attr.orig before I changed it

> but it is owned by root so that's no help.

Your best option is to boot from a CD (installation cd for example), drop to a shell, mount the rootslice and fix your mistakes.

LionO at 2007-7-5 18:48:22 > top of Java-index,General,Sys Admin Best Practices...
# 2
(I realise this is probably a bit late now - you've probably reinstalled many times over since.)You should have been able to boot to single user/maintenance mode, and then login with the root password - the sulogin program doesn't use PAM.
jrg_work at 2007-7-5 18:48:22 > top of Java-index,General,Sys Admin Best Practices...
# 3
But without all the root credentials that wouldn't have been very usefull. Besides; there really is no need to reinstall what so ever. Just use the install cd to get to a shell, mount the rootslice and re-edit the user_attr file is all it takes.
LionO at 2007-7-5 18:48:22 > top of Java-index,General,Sys Admin Best Practices...