DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=MIdx+JueAk/ltmqNAJHwW7bvnXdmr
	qAKJCiAVyKhIppvd+TFlSHgI7lO14H3BcrYb7uzJYGmlWwRCzC077w0ZLWg883u8
	PP4CF3VDmp8OjnPCV4qDrOT4Mgrc4SwtRPInrEq1RdNlLKKltBNU6tjIwukdhv4L
	XWptBbi6nv184A=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Habermann, David (D)" <DAHabermann@dow.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.5
Date: Wed, 5 Nov 2014 18:23:54 +0000
Message-ID: <C9D37D92E903B347A31B9CF82643BA280730A5ED@046-CH1MPN1-043.046d.mgd.msft.net>
References: <announce.20141105111753.GT28636@calimero.vinschen.de>
In-Reply-To: <announce.20141105111753.GT28636@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Received-SPF: None (protection.outlook.com: dow.com does not designate permitted sender hosts)
Content-Transfer-Encoding: 8bit

> I just released a 5th TEST version of the next upcoming Cygwin release,
> 1.7.33-0.5.

Ever since using this 1.7.33-0.x series (currently running 1.7.33-0.5) I've been having intermittent trouble with one of my scripts, and just finally got around to digging further today.  This is an expect script (subroutine of a larger system) designed to auto-login to an ssh session and then set the passwd -R to allow further ssh sessions to have "full network powers". (I then run a cron script which drops these rights off again every half-hour, so the "full network powers" logins are time limited.)

The symptoms of the failure are that it sometimes fails to send the ssh password (and thus doesn't proceed to the passwd -R command at all).  If I run the script a second time, it almost always works on the second try. After some time has passed I run it again and get a failure, then immediately run again and succeed.  I would appreciate any thoughts as to why such a script would fail, and then succeed on successive runs.  This routine basically never failed on the previous recent versions of cygwin (in active daily use since approximately July 1st).

Dave


The script is called like this:

$ super.exp localhost mypasswd

and the file super.exp looks like this:

#!/usr/bin/expect

set mach [lindex $argv 0]
set pass [lindex $argv 1]

spawn ssh -o PubkeyAuthentication=no $mach
expect -exact "password: "
send $pass\n
expect {
        "$ " {
                send "passwd -R\n"
                expect -exact "password: "
                send $pass\n
                expect -exact "password: "
                send $pass\n
                expect -exact "$ "
                send "exit\n"
                interact
        }
        "Permission denied, please try again." {
                send_error "The password you provided was invalid.\n"
                exit 1
        }
}