While playing with my test box, I noticed an odd quirk in hostbased authentication. If the destination user's shadow entry has a "*LK*" as their password, then hostbased auth will fail and I'm prompted for a password that also fails. If the password field is "*LK" then hostbased auth works fine. This seems like it may have been designed in, since under Solaris (maybe others) accounts have a shadow password of *LK* when they're first created but not yet given a password. Then again, it's not documented anywhere so I thought it may be a bug worth mentioning. Either way, perhaps this belongs in the FAQ in the "It's asking for password despite .rhosts" section. -- Gregor Mosheh [EMAIL PROTECTED] Systems Admin, Humboldt Internet 707.825.4638
