Thanks. It is basically as I was thinking. I don't entirely grok why a person would be concerned about the name of a file. Well, unless they make file names like "job_application_to_major_competitor.odt" on the work system. Well, maybe the contents of ~/.ssh where the names of the private keys could possibly be of some interest to a cracker in the "is is worth my while to bother?" sense.
Thanks. I often need help in getting my head around some things. Especially since I more a z/OS (back to the OS/MVT days) sysprog. And especially thanks for the reminder about ACLs. I do use them, on z/OS, on rare occasion (z/OS Web server). Hum, wonder if I should record the ACLs for a given file in another table in the same data base. For use by security administrators. That would be adding in a new function. And I'm not sure if it would be very useful. That might require integrating in the /etc/password type information to do a reverse look up of the stored uid and gid. Assuming I want this data base to be used by auditors / security administrators. So I will go with the wiser heads of the UNIX wizards of the past and present and keep the data base file locked away in a non-world readable subdirectory. -- I have _not_ lost my mind! It is backed up on a flash drive somewhere. Maranatha! <>< John McKown ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
