From: "Steven Hartland" <killing@multiplay.co.uk>
To: "Cygwin List" <cygwin@cygwin.com>
Subject: cygwin getpass broken recently? was: cygrunsrv fails to prompt for user password
Date: Sat, 07 Jul 2012 04:05:00 -0000 [thread overview]
Message-ID: <87292535788F4E2CB162C788878399B8@multiplay.co.uk> (raw)
In-Reply-To: <A72317022EF94931BECDB5D98449361C@multiplay.co.uk>
----- Original Message -----
From: "Steven Hartland"
> We're updating our servers to a newer version of cygwin (1.7.15)
> from previous 1.7 version and in this version the install of
> cygrunsrv (V1.40, Apr 25 2012) fails to correctly prompt for
> a user password even though -u <username> is being specified.
>
> It seems like cygrunsrv maybe checking for an "interactive"
> session and incorrectly determining its not as in our case
> we are running the cygrunsrv via ssh e.g.
>
> ssh "cygrunsrv ...."
>
> We know that this worked correctly in cygrunsrv V1.34, Mar 18
> 2008.
>
> Bug introduced recently?
After inspecting the code for cygrunsrv and adding some debug
I've determined this isn't a bug in the util but in cygwin's
getpass function which I believe may have been changed
recently by Corinna Vinschen, after googling around.
Is this a new issue caused by these changes Corinna?
Regards
Steve
--
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
next prev parent reply other threads:[~2012-07-07 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 17:39 Steven Hartland
2012-07-07 4:05 ` Steven Hartland [this message]
2012-07-09 12:39 ` cygwin getpass broken recently? was: " Corinna Vinschen
2012-07-09 13:01 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87292535788F4E2CB162C788878399B8@multiplay.co.uk \
--to=killing@multiplay.co.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).