Re: SUMMARY sort of: OpenSSH public key authentication woes

[Larry Hall <cygwin-lh at cygwin dot com>]

At 11:21 AM 4/27/2004, you wrote:
>On Tue, 27 Apr 2004, Greg Rudd wrote:
>
>> On Tue, 27 Apr 2004 02:12 am, Karl M wrote:
>> > Hi Greg...
>> >
>> > Try setting your authorized_keys to 644 for now. If that doesn't work, take
>> > a look at the problem reporting section on the Cygwin web page. This list
>> > would need more information to help further.
>> >
>> Doing the above does allow a local user to public key authenticate :-) but
>> when I try to do the same thing with a domain user public key still fails but
>> what is interesting is when I try to set the acl's for the .ssh directory to
>> be the same as the local users the setfacl command fails with a error message
>> setfacl function not implemented.  I notice that this message comes up when
>> the ssh-user-config command is run for the first time.
>>
>> Is this error message occuring because the domain users home directory is
>> mapped to a unc (which in this case is //machine/grudd) instead of a path
>> name in the form of "/home/grudd"
>
>Most likely.  Add "smbntsec" to your CYGWIN environment variable.  Also,
>you can hide the fact that it's on a remote machine by using "mount -s
>//machine/grudd /home/grudd".
>HTH,
>    Igor
>


But (anticipating the next question) the domain user won't be able to see
your share through ssh and pubkey authentication unless it doesn't require 
Windows authentication to access it (i.e. it's accessible by "Everyone").


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/