Sven I've just gone through the home directories - none of them have spaces in them. Some of them have a period "." in their name though - would this break the script? The only other different thing I do is that I put home directories into groups, so User A, Group A would have his homedir /home/groupa/usera for eg. I also have many users that have no home directories - they are POP3 users so they are /bin/false. Would this also be an issue? Thing is, I've never had the secchk script give this problem before until last week ... perhaps a new user I created might have broken the script ... just trying to figure out how ... Regards Luke -----Original Message----- From: Sven 'Darkman' Michels [mailto:sven@darkman.de] Sent: Monday, 12 May 2003 9:00 AM To: suse-security@suse.com Subject: Re: [suse-security] Seccheck script errors - anything I need to worry about? Luke Loh wrote:

My knowledge of awk is limited so I can't figure out what is wrong except that it's related to the ${homedir} variable.

Is this something I should worry about? Should I just reinstall seccheck or is there something I need to investigate?

Maybe you have spaces in the usernames/homes? like /home/bla fasel/? think that would cause it. HTH Sven -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here