Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Password echo to console under Cygwin MinTTY.(Windows) #52

Open
rctrh opened this issue Dec 10, 2015 · 6 comments
Open

Password echo to console under Cygwin MinTTY.(Windows) #52

rctrh opened this issue Dec 10, 2015 · 6 comments

Comments

@rctrh
Copy link

rctrh commented Dec 10, 2015

Under a Cygwin installation on Windows (the terminal window is Mintty, running bash by default), the password is echoed. There is a message about fixing your stdin.

It seems like something isn't quite working right. The terminal is functional enough that other programs like ssh (openssh) for example, doesn't have a problem changing the terminal settings to disable echo.

I'm not sure where to start debugging this. The cygwin environment includes stty.

I have a vague recollection of this working properly in the past, possibly in the 1.0 time frame.

@strzibny
Copy link
Contributor

Can you include the plugin version used and some steps for setting this environment on Windows?

@rctrh
Copy link
Author

rctrh commented Dec 14, 2015

Registration version 1.0.1, Cygwin MinTTY 1.1.3, Bash 4.1.10, Windows 7/64 bit.
Box: rhel-cdk-kubernetes-7.2-6.x86_64.vagrant-virtualbox.box (cdkv2 beta 3)

$ vagrant plugin list
vagrant-adbinfo (0.0.5)
  - Version Constraint: 0.0.5
vagrant-registration (1.0.1)
vagrant-share (1.1.4, system)

$ vagrant version
Installed Version: 1.7.4
Latest Version: 1.7.4

You're running an up-to-date version of Vagrant!

$ bash --version
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
Copyright (C) 2009 Free Software Foundation, Inc.

$ mintty --version
mintty 1.1.3
(C) 2013 Andy Koppe

@rctrh
Copy link
Author

rctrh commented Dec 14, 2015

Here's the output from vagrant up:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 2376 => 2379 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default:
    default: This is not an error message; everything may continue to work properly,
    default: in which case you may ignore this message.
==> default: Registering box with vagrant-registration...
    default: Would you like to register the system now (default: yes)? [y|n]y
    default: username: foo
    default: password:
Error! Your console doesn't support hiding input. We'll ask for
input again below, but we WILL NOT be able to hide input. If this
is a problem for you, ctrl-C to exit and fix your stdin.
     default: password:

Note: I didn't hit enter twice, it printed the password prompt, then the error about stdin, then the password prompt again.

@strzibny
Copy link
Contributor

Definitely something to look at. @pvalena can hopefully try to run it on Windows now or soon enough.

@optak
Copy link

optak commented Feb 3, 2016

no problem when running vagrant up under cmd.exe

@rctrh
Copy link
Author

rctrh commented Feb 3, 2016

The problem is with Cygwin. I seem to recall, this worked fine in the CDK 1.0 timeframe.

Unless Cygwin isn't considered a valid environment, this should be considered a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants