Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <911C684A29ACD311921800508B7293BA037D2A06@cnmail>
From: Mark Bradshaw <bradshaw AT staff DOT crosswalk DOT com>
To: "'Corinna Vinschen'" <cygwin AT cygwin DOT com>
Subject: RE: openssh issue with UID's over 65535
Date: Tue, 15 Jan 2002 05:44:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain

How about a patch to mkpasswd to do this?  Would you be interested?

> -----Original Message-----
> From: Corinna Vinschen [mailto:cygwin AT cygwin DOT com] 
> Sent: Tuesday, January 15, 2002 5:35 AM
> To: 'cygwin AT cygwin DOT com'
> Subject: Re: openssh issue with UID's over 65535
> 
> 
> On Mon, Jan 14, 2002 at 08:12:00PM -0500, Mark Bradshaw wrote:
> > I have an issue with openssh and UID's over 65535.  Similar things 
> > were discussed a bit back, but this is slightly different.  
> Seems that 
> > sshd will die when a user with a UID too high logs in.  The 
> root cause 
> > of this is cygwin's use of an unsigned short for uid_t, 
> instead of an 
> > integer.  As the UID goes through the ssh server, session.c calls 
> > get_last_login_time
> > (sshlogin.c) with an integer variable.  When it hits 
> get_last_login_time,
> > however, it's squashed into a uid_t, which is too small for 
> it.  The uid
> > changes and problems occur.
> > 
> > I'm guessing it wouldn't be too swift to just change the 
> definition in 
> > types.h.  That oughta break lotsa stuff.  Is there some 
> clear path to 
> > getting uid_t changed to an int, or is there a different/better fix 
> > for this?
> 
> Change the UIDs in /etc/passwd to be smaller than 65536.
> 
> Changing uid_t to unsigned int would break almost all Cygwin 
> applications.  We wouldn't be backward compatible.  We can't 
> do this.  At least at this point.  I would expect some more 
> really interesting changes in Cygwin before breaking backward 
> compatible.
> 
> 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/
> 

--
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/