X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Ng Subject: Re: 1.7.1: problem with public key authentication on domain accounts Date: Fri, 15 Jan 2010 11:42:54 +0000 (UTC) Lines: 37 Message-ID: References: <18e742db1001050839p78fe787xb583efc616490744 AT mail DOT gmail DOT com> <20100107162003 DOT GI23972 AT calimero DOT vinschen DOT de> <20100114185400 DOT GJ14511 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Corinna Vinschen cygwin.com> writes: > > On Jan 14 17:32, Andrew Ng wrote: > > What I did was to change the group of my domain user to be "Administrators" > > in > > "/etc/passwd" rather than the domain group. This stops the following error > > from > > occurring every time I try to ssh to my machine as my domain user: - > > > > 1 [main] -tcsh 13776 C:\Cygwin\bin\tcsh.exe: *** fatal error - > > couldn't > > dynamically determine load address for 'WSAGetLastError' (handle 0xFFFFFFFF), > > Win32 error 126 > > > > In fact making the group "Users" also works fine, just not the domain group. > > Using the domain group seems to result in no file access permissions to the > > system libraries and hence the error above when starting the "tcsh" shell. > > > > This isn't ideal as I would really prefer to be using the domain group but > > it's > > better than having to start sshd manually which was my previous workaround. > > By > > the way I'm running on Windows XP Pro x64 SP2. > > http://cygwin.com/ml/cygwin/2010-01/msg00334.html > > Corinna > Thanks for the link. That does explain what's going on in this situation. I think your suggestion of adding the local BUILTIN\Users group would be nice. I'm not too sure our IT will be too keen on adding a domain user for Cygwin sshd purposes. Regards, Andrew -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple