Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Son of son of SSH & Cygwin; scp and sftp
Date: Mon, 9 Sep 2002 11:49:29 -0400
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E10AACC@ex02.idirect.net>
From: "Harig, Mark A." <maharig AT idirect DOT net>
To: "Stephen C. Biggs" <yyyyy50 AT hotpop DOT com>, <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

It's been a month.  I have gotten mine to work.  (No, I haven't
been working on it for a month :))

I am able to ssh from a PC running Win2K in one NT domain to
another PC running Windows NT in a different NT domain.  The problem
was that my 'pw_gecos' field in my password entry needed to be changed
so that the domain (that is, the U-WHATEVER-YOUR-NT-DOMAIN-IS) value
was appropriate for the the machine on which the /etc/password file
resides.

In the hope that this will help other people with this problem, here
are the steps I took, assuming my account is 'joe_user':

A. In NT domain 'FOO':

   1. Generate an entry for /etc/passwd using:

      $ mkpasswd -d | grep 'joe_user' >> /etc/passwd

      This entry contain 'U-FOO' among other values in the 'pw_gecos'
      field.

   2. Copy my password entry (via email, floppy, whatever) to the
      machine in NT domain 'BAR'.

   3. Generate a public/private encryption file key pair in 
      ~joe_user/.ssh, using, for example, ssh-keygen.

   4. Copy my public encryption key to the PC in NT domain 'BAR'.

B. In NT domain 'BAR':

   1. Edit /etc/passwd, adding the new entry for 'joe_user' from
      NT domain 'FOO'.

   2. Edit my new entry, changing the 'U-FOO' to 'U-BAR'.

   3. Setup an ssh daemon/server using /usr/bin/ssh-host-config.

   4. Start the ssh server, using 'cygrunsrv'.

The environment variable CYGWIN includes 'ntsec' (among other values)
and the file system on both PCs is NTFS.

After these steps, knowing the IP address of the machine in NT domain
'BAR', I am able to run an ssh client in NT domain 'FOO' and connect
to the machine in NT domain 'BAR'.

Now the question is: how can a test be devised to check for this
problem/error?  The error message from ssh (i.e., "connection closed")
doesn't give the user any idea where the problem might be.

> -----Original Message-----
> From: Stephen C. Biggs [mailto:yyyyy50 AT hotpop DOT com]
> Sent: Thursday, August 08, 2002 9:10 AM
> To: cygwin AT cygwin DOT com
> Subject: Re: Son of son of SSH & Cygwin; scp and sftp
> 
> 
> On 8 Aug 2002 at 11:10, Corinna Vinschen wrote:
> 
> > On Wed, Aug 07, 2002 at 03:03:31PM -0700, Stephen C. Biggs wrote:
> > > On 7 Aug 2002 at 15:02, Corinna Vinschen wrote:
> > > 
> > > > On Mon, Aug 05, 2002 at 04:34:44PM -0700, Stephen C. 
> Biggs wrote:
> > > > > Fanfare!!!
> > > > > You are successfully logged in to this server!!!
> > > > > setgid: Invalid argument
> > > > 
> > > > It looks as if the gid given in your /etc/passwd entry is not a
> > > > valid group in /etc/group.
> > > 
> > > Where?  On the server or the client?
> > 
> > On the server.
> > 
> > >   Does the group on the client have 
> > > to exist on the server?  
> > 
> > No.
> > 
> > >   Because the groups are valid in both places!
> 
> I misspoke.. the group on the cygwin box was 513 which didn't have a 
> group entry...  Changing it to a valid group, I now don't get 
> the setgid 
> error, just the server dumping the connection, like usual.
> 
> > 
> > Corinna
> > 
> > -- 
> > Corinna Vinschen                  Please, send mails 
> regarding Cygwin to
> > Cygwin Developer                                
> mailto:cygwin AT cygwin DOT com
> > Red Hat, Inc.
> > 
> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/