Key 'OPENSSH' is not supported
I'm trying to use the option of Pair to Mac on my Windows (Windows 10 Enterprise Version 1709 Build 16299.655) Visual Studio 2017 Professional to connect to my MAC (macOS Mojave Version: 1014.1). I'm able to SSH connect through CMD, Powershell and VS Developer Cmd Prompt. Also I'm able to setup Cross Platform connection to my MAC, but when I use the option Pair to MAC it tells me that "Key 'OPENSSH' is not supported"
Add Comment
Hi! I have the same issue, running Visual Studio 2017 15.8.8 on Windows 10 Enterprise Version 1803 Build 17134.345. When pairing my PC to the Mac I get the error message "Key 'OPENSSH' is not supported" after entering user credentials.
I have attached the log file found at %LOCALAPPDATA%\Xamarin\Logs\15.0\2018-11-05-14-31-2779288ide.log
@Nicklas Rosvall Carlquist can you confirm the macOS name and version that you are using?
I am running macOS Mojave 10.14.1 on my Mac mini
Hi,
We are investigating this issue since we already have an internal report that can be reproduced on certain Windows machines.
It would be helpful if you could zip and share the content of the following folder: %LOCALAPPDATA%\Xamarin\MonoTouch.
Thanks.
I can reproduce this issue by creating a new user in Windows and use it to pair with Mac. Here is the files you want. Hope it helps.
Paul, could you please share you Ide.log from %LOCALAPPDATA%\Xamarin\Logs\15.0?
Please attach the one corresponding to the VS session that you reproduce the issue. I think you repro has a different root cause than the others, but just to confirm.
Thanks
I'm having the same issue. Windows 10 Pro 10.0.17134, Macbook Pro 13 2017 MacOS Mojave version 10.14.1. Happened after upgrading to VS 15.8.9 from (I think) 15.8.3.
Problem also exists in 15.9.0 Preview 4.
A quick resolution will be greatly appreciated because this is causing us real issues.
Ide log message:
Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Checking Xamarin iOS installation... Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Checking host configuration for connecting to 'TheMac'... Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Server State transition from ConfiguringState to ConfiguredState on TheMac (192.168.0.20) Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Host 'TheMac' is configured correctly Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Server State transition from ConfiguredState to ConnectingState on TheMac (192.168.0.20) Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Starting connection to 'TheMac'... Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Starting connection to 'TheMac'... Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Server State transition from ConnectingState to DisconnectingState on TheMac (192.168.0.20) Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Starting disconnection from TheMac... Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Starting disconnection from TheMac... Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Server State transition from DisconnectingState to DisconnectedState on TheMac (192.168.0.20) Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|The connection to 'TheMac' has been finished Xamarin.Messaging.Integration.State.ServerStateContext|Error|0|Couldn't connect to TheMac. Please try again. System.NotSupportedException: Key 'OPENSSH' is not supported. at Renci.SshNet.PrivateKeyFile.Open(Stream privateKey, String passPhrase) at Renci.SshNet.PrivateKeyFile..ctor(String fileName, String passPhrase) at Xamarin.Messaging.Ssh.MessagingAuthenticationMethod.InitializePrivateKeyAuthentication(String username, ISshInformationProvider sshInformationProvider) in E:\A_work\675\s\External\messaging\src\Xamarin.Messaging.Ssh\MessagingAuthenticationMethod.cs:line 76 at Xamarin.Messaging.Ssh.MessagingService.GetMessagingConnection(Func`1 passwordProvider, ISshInformationProvider sshInformationProvider) in E:\A_work\675\s\External\messaging\src\Xamarin.Messaging.Ssh\MessagingService.cs:line 418 at Xamarin.Messaging.Ssh.MessagingService.<ConnectAsync>d__64.MoveNext() in E:\A_work\675\s\External\messaging\src\Xamarin.Messaging.Ssh\MessagingService.cs:line 167
The issue has been identified and it has to do with the OpenSSH version that comes in the macOS Mojave 10.14.1. Given that the SSH keys that VS uses to authenticate are generated in the Mac and then copied to Windows, if we generate a pair of SSH keys with Mojave 10.14.1, then the SSH library that Xamarin uses in VS doesn't support this new OpenSSH format yet, so it can't read the SSH keys and it fails to authenticate to the Mac.
We are already working on a fix until the SSH library adds the real support for this. By now, the only workaround to apply is possible if you have abother Mac machine with a macOS version lower than 10.14.1. In this case the workaround is:
1 - Remove the folder %LOCALAPPDATA%\Xamarin\MonoTouch, this will clean the current SSH keys used to authenticate
2 - Try to connect from VS to a Mac with a macOS lower than 10.14.1. This will re generate the SSH keys with a supported format that our SSH library can read to authenticate
3 - Once connected and the keys present in the MonoTouch folder again, try connecting to the real Mac with Mojave 10.14.1. At this point the SSH keys are already present so they will not be generated again, so you will be able to connect.
As mentioned, we are working on a real fix and push it soon. We will keep you updated.
Thanks.
I can confirm that this workaround does work and resolved my issue. please let us know if a fix is in place in the future. thanks!
We don't have another Mac we can use, so please continue to work on a fix. If it could be fixed in 15.9 Preview quicker than 15.8 that would work for us too. Thank you.
I'm sorry to hear that you can't apply the workaround. Additionally, the workaround doesn't affect the fix progress. In fact, the fix is already in place and waiting to pass the approval process to be included in d15-9. Thanks.
We have fixed the problem in an upcoming release. Thank you for your feedback!
Thank you, when can we expect it to be release?
This is a show stopper for me as well. Is there plans for this issue to be resolved in a stable or preview release within the next week or so?
Hi, John & Tyler -- I can't promise an exact date (I'm still finalizing the fixes to go into the servicing releases), but I definitely want to get this into the first substantive update, and reasonably soon. Sorry I can't be more specific yet!
A fix for this issue is now available in the latest preview, Visual Studio 2019 Preview: https://visualstudio.microsoft.com/vs/preview/ , which can be installed side-by-side with your existing instance of Visual Studio 2017. To learn more on how the Visual Studio 2019 preview can help you to be more productive, please visit https://blogs.msdn.microsoft.com/visualstudio/2018/12/04/making-every-developer-more-productive-with-visual-studio-2019/ .
