Hi after more investigation I think this is a Win32-openssh bug. Putty works with Vagrant just fine – no issues.
When I use the openssh-win32 port directly to ssh to a box – I still loose arrow key functionality. I will report on their site – thanks for the help. Take care Sent from Mail for Windows 10 From: Alvaro Miranda Aguilera Sent: Friday, April 1, 2016 12:10 AM To: Jeremy Hajek Cc: [email protected] Subject: Re: [vagrant-up] Windows 10 using Win32 Openssh port, loose arrowkeyfunctionality hello, When you do vagrant ssh-config you will be shown the configuration for ssh. ie port and key when you conntect there using putty to that vm, do you have the arrow key issue? On 1/04/2016, at 6:39 AM, Jeremy Hajek <[email protected]> wrote: Hi thanks for the response. Vagrant works fine with using Putty – which makes me think that it is a bug either Vagrant or Openssh-win32 Take care Sent from Mail for Windows 10 From: Alvaro Miranda Aguilera Sent: Wednesday, March 30, 2016 10:03 PM To: [email protected] Subject: Re: [vagrant-up] Windows 10 using Win32 Openssh port, loose arrow keyfunctionality what happen when you ssh using putty? Alvaro. On Thu, Mar 31, 2016 at 4:57 AM, Jeremy Hajek <[email protected]> wrote: Hello, I am using Windows 10, Vagrant 1.8.1, and VirtualBox 5.0.10 r104061 ssh -V renders this: OpenSSH_7.1p1 Microsoft_Win32_port_with_VS Mar 19 2016, OpenSSL 1.0.2d 9 Jul 2015 I installed the Microsoft Win32 port of SSH to native Windows (not cygwin or git) https://chocolatey.org/packages/win32-openssh It installs fine and I have native SSH now in powershell able to use in Windows. When I issue a vagrant up command and then a vagrant ssh I can enter the virtual machine - but the arrow keys stop working inside of the virtual machine/vagrant box. Every other key works fine and I can recreate this in every single vagrant box. Would this be a vagrant ssh issue or is this a Win32 ssh issue? What is your opinion? take care Jeremy Hajek -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/849c8c67-dea7-4bf9-9080-5a3e6a710860%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/nFBr6aguCp4/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey5MUF2twab4%3D1O7DLo9vmQMQDYpnQJTuGj9SsBnEyTtg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/56fead63.c6d10d0a.f164b.3fe0%40mx.google.com. For more options, visit https://groups.google.com/d/optout.
