> 3) Make sure your authorized_keys file has permissions of 600 This is not so if you are using ntsec. It may if you are not using ntsec and is required for unix. The file needs to be readable by the local system account (or whatever account ssh is running under). Unlike unix, the local administrator (or any administrator) still has to have read permissions to a file to read it. If you deny read privileges to to the local system, it can't read the file and can't authenticate you with public keys.
This is one of those idiocies of windows. An administrative user can take ownership of the file and read it but not just read it. Of course MS also claims that you can't chown a file to belong to another user so you can tell if the admin has been reading your files because they all belong to him. Of course this is a lie and there are plenty of chown type programs out there (not by MS) that do it. But it makes the CEOs feel more secure I guess. Trying to protect anything from a user who has privileges to modify the running kernel seems rather silly... >>>------> -- +-------------+-----------------------+---------------+ | Ed Schaller | Dark Mist Networking | psuedoshroom | +-------------+-----------------------+---------------+
signature.asc
Description: Digital signature
____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
