The file tiger/systems/Linux/2/file_access_list appears to have been 
autogenerated with some problems.  I am using the 3.2.1 package of Tiger 
under Debian 4.0.  The autogeneration comment is the implication from 
something I recall reading but cannot find right now.  I will include a couple 
of examples:

file               owner     group  s  g  r  w  x  r  w  x  r  w  x   LVL  
OwnID  GrpID  
PermID
/bin/*             root      root   .  0  1  1  1  1  0  1  1  0  1.  001  002  
  003
/root/.rhosts      jfernand  root   0  0  1  1  0  1  0  0  1  0  0   W    006  
  006    
006

Although I do not think it causes a problem, the column header line should 
probably be a comment line instead, meaning start with "#file".  If nothing 
else, it probably avoids the check_perms script from evaluating that line.

Most of the problems seemed to be around spaces missing between 
other/world x and LVL, such as /bin/* above.  This was relatively easy to 
restore.  There were spaces missing between the remaining columns but 
that is cosmetic.

For myself, I changed the ownership of /root/.rhosts ownership back to root.

There are also two entries for /bin and three entries for /usr.  One version 
for 
/usr was missing a part.  In general, these duplicat entries were equivalent.  
There was a difference between "." and "W" in the LVL column but in looking 
at the check_perms script it appears that neither "." or "W" are checked for 
explicitly so it behaves the same as the default, which is "W".

Thank you,

Doug Peterson



_______________________________________________
Tiger-user mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/tiger-user

Reply via email to