On 06/15/09 10:29, Kevin Pan wrote: > Hi, > > I'm trying to configure a new server running Solaris 10 05/09. I'd like to > fingerprint the system "just in case" as a security measure. I executed the > command as root user "bart create" and it churned out a bunch of output (it > is much longer but I copied only a few lines for brevity). I repeated the > sames process on OpenSolaris 2009.06 and the result is the same. > > /var/tmp/orbit-admin/linc-63a-0-4a3585a1f0fea S 0 140755 > owner@::deny,owner@:read_data/write_data/append_data/write_xattr/execute/write_attributes/write_acl/write_owner:allow,group@:write_data/append_data:deny,group@:read_data/execute:allow,everyone@:write_data/append_data/write_xattr/write_attributes/write_acl/write_owner:deny,everyone@:read_data/read_xattr/execute/read_attributes/read_acl/synchronize:allow > 4a35e54d 101 10 > /var/tmp/orbit-admin/linc-6fe-0-4a365a226ff3e S 0 140755 > owner@::deny,owner@:read_data/write_data/append_data/write_xattr/execute/write_attributes/write_acl/write_owner:allow,group@:write_data/append_data:deny,group@:read_data/execute:allow,everyone@:write_data/append_data/write_xattr/write_attributes/write_acl/write_owner:deny,everyone@:read_data/read_xattr/execute/read_attributes/read_acl/synchronize:allow > 4a3601b9 101 10 > /var/tmp/wscon-:0-AwaaLb F 403 100600 > owner@:execute:deny,owner@:read_data/write_data/append_data/write_xattr/write_attributes/write_acl/write_owner:allow,group@:read_data/write_data/append_data/execute:deny,group@::allow,everyone@:read_data/write_data/append_data/write_xattr/execute/write_attributes/write_acl/write_owner:deny,everyone@:read_xattr/read_attributes/read_acl/synchronize:allow > 4a3601b2 0 0 90a34cec7ad1a7769a52d5dfa7b462e8 > /var/yp/aliases F 1062 100555 > owner@:write_data/append_data:deny,owner@:read_data/write_xattr/execute/write_attributes/write_acl/write_owner:allow,group@:write_data/append_data:deny,group@:read_data/execute:allow,everyone@:write_data/append_data/write_xattr/write_attributes/write_acl/write_owner:deny,everyone@:read_data/read_xattr/execute/read_attributes/read_acl/synchronize:allow > 4a0c3e32 0 2 18fd15900821ac172cab38791cd46dd1 > /var/yp/nicknames F 226 100644 > owner@:execute:deny,owner@:read_data/write_data/append_data/write_xattr/write_attributes/write_acl/write_owner:allow,group@:write_data/append_data/execute:deny,group@:read_data:allow,everyone@:write_data/append_data/write_xattr/execute/write_attributes/write_acl/write_owner:deny,everyone@:read_data/read_xattr/read_attributes/read_acl/synchronize:allow > 4a0c3e32 0 2 034820835249426d8982612207ed5539 > > Does anyone knows what that is?
Yes, this is the "manifest" (see bart_manifest(4)) that bart creates in response to your command # bart create What did you expect? ;-) You probably want to save this output somewhere for future comparisons. Joep