/etc/passwd file security

[Andrew Luis Arruza]

Our Data Security people enter the Social Security Number of users in one of the optional fields when entering new users. This is required for identification purposes with the BMC program we use.
Problem: How can I keep others from viewing the /etc/passwd file? Some of the DBA's are very leary about their SSN being viewable by all. This file has to be readable by all if I am correct.
Any ideas will be greatly appreciated.
Points assigned--as always!! Andy

[Chris Calabrese · Accepted solution]

Very bad things will happen if you make /etc/passwd non-world-readible. I suggest putting this somewhere other than /etc/passwd or using something other than SSN's (which you have a legal obligation to keep private).

[Patrick Wallek]

Hmmm.....I don't like where this is going. You can't make the passwd file so it is not readable by everyone. Things won't behave well. Having SSNs in the passwd file is a VERY BAD idea. If you really want to get technical with the law, you CAN NOT use someones SSN for identification purposes. The only thing the SSN can be used for is for it's purpose, Social Security. The law isn't enforced well, but as far as I know that is the law.

Even going to a trusted system won't help you in this case as the password field is the main information that is kept in the /tcb directory. The /etc/passwd still has to be readable by all.

Why does the BMC stuff need an SSN? That seems VERY strange to me. I'd look at assigning an employee id # that is something other than the SSN. At my present employer, the numbers that someone came up with were z######. This number was used for ALL company business. The only thing that need the SSN was the W-4 (I think) form for the IRS.

I'd say you are on very shaky ground with the SSN issue. If someone were dishonest, all they really need is a name and an SSN and they can really cause a person some major problems with their credit rating, and a host of other things.

Something to think about.