You're a genius, Erik!
Adding the String Value C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe for DefaultShell under HKEY_LOCAL_MACHINE\SOFTWARE\OpenSSH in the registry did the trick (DefaultShell needs to be created there first - it doesn't exist yet).
Clearly that left me with a working solution. But now I got adventurous: I directed ssh to use the bash.exe that came with giit (in the Git/bin directory) as the DefaultShell. This worked too. I thought maybe git will be happier in its "native" bash environment for potential future issues. But either one will work for cloning repositories from a Windows box.
Now the remaining question (for you maintainer guys): Do you want to call that a fix or a workaround? If it is the latter (which would get my vote), then someone would still need to touch git under Windows to make it also work with cmd.exe, not just bash.exe or powershell.exe; in other words, this case is then not closed, even though everything is now working for me. Having the user change registry entries doesn't seem like a good solution to me - neither does changing the registry entries of a different program (OpenSSH in this case) during installation of git for Windows. But that's obviously not my call - just voicing my opinion. I am not familiar with your Change Request Management process/etiquette.
Most important of all, however: Thank you Erik for sharing your valuable experience and getting me up and running again - it is very highly appreciated!!!
Ekkehard
Show 16 quoted lines
> On Oct 20, 2022, at 23:06, Erik Cervin Edin <erik@cervined.in> wrote:
>
> On Fri, Oct 21, 2022 at 12:00 AM W. Ekkehard Blanz
> <ekkehard.blanz@gmail.com> wrote:
>>
>> How do I convince git to use Powershell as its shell of choice when it arrives over ssh at my target Windows box? Unfortunately,
>> git help clone
>> Does not give me any indication how to do that.
>
> AFAIK, the remote choses the default shell of ssh sessions so you
> either change that or somehow launch a different subshell with the
> client. The former should be easier
> https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_server_configuration
> the latter is talked about somewhere in here
> https://github.com/PowerShell/Win32-OpenSSH/issues/752
> if my memory serves me correctly. I chose the former