delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/04/19/14:05:14

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <480A3437.1080100@cwilson.fastmail.fm>
Date: Sat, 19 Apr 2008 14:04:39 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: [Avail for test] login-1.9-8
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

There is a new version of the 'login' package available on the mirrors. 
The current version, 1.9-7, does not allow ~/.rhosts-based passwordless 
authentication when the rlogin server is running as any user other than 
SYSTEM.

On Vista, you have to run the rlogin server as a special privileged 
user, because SYSTEM no longer has the necessary permissions to setuid 
to the newly logged-in user.

These conflicting requirements meant that you could not use ~/.rhosts 
authentication to log in to a Vista machine.

There is quite a lot of new code added to this implementation, so if you 
run telnetd or rlogind servers under cygwin, please test that this 
version of login causes no problems for you. (unfortunately, sshd does 
not invoke login as part of its process -- it has to be telnetd or rlogind.)

I'd especially like success reports from the following configurations. 
Be sure and tell me which OS (and OS variant: Home, Professional, 
Ultimate, etc) and service pack level you're using.

  1) Windows XP, inetutils-1.5-3 daemons running under SYSTEM
  2) Windows XP, inetutils-1.3.2-40 daemons running under SYSTEM
  3) Windows 2k, inetutils-1.5-3 daemons running under SYSTEM
  4) Windows 2k, inetutils-1.3.2-40 daemons running under SYSTEM
  5) Windows NT, inetutils-1.5-3 daemons running under SYSTEM
  6) Windows NT, inetutils-1.3.2-40 daemons running under SYSTEM
  7) Windows 9x + inetutils-1.5-3
  8) Windows 9x + inetutils-1.3.2-40
  9) Windows Server 2003 + inetutils-1.5-3 daemons [*]
10) Windows Server 2003 + inetutils-1.3.2-40 daemons [*]
11) Windows Server 2008 + inetutils-1.5-3 daemons [*]
12) Windows Server 2008 + inetutils-1.3.2-40 daemons [*]
13) Windows Vista + inetutils-1.5-3 daemons [*]
14) Windows Vista + inetutils-1.3.2-40 daemons [*]

[*] daemons here must run under a special privileged user account, not 
SYSTEM.  The inetutils-1.5-3 iu-config script will (create the account 
if necessary, and) install the inetd service under an appropriate 
account for you. You'll have to do it manually for inetutils-1.3.2-40.

It's not that I need reports from all these configuration before making 
this new version of login current; but a decent variety of success 
reports would be a good thing...

--
Chuck


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019