Wanted to discuss the issues OpenSSH is causing lately.
repo.msys2.org: #2388Possible solutions:
repo.msys2.orggit-with-openssh manifest silentlyversion property shows GIT version instead of OpenSSHgit-with-openssh (Example: rivy/openssh)version property shows OpenSSH versionwin32-openssh silentlygit-with-openssh via depends property?json
{
"homepage": "https://git-for-windows.github.io/",
"url": "https://git-for-windows.github.io/",
"license": "GPL-2.0",
"version": "7.7p1",
"suggest": {
"Git with OpenSSH": [
"git-with-openssh"
],
"Portable OpenSSH": [
"win32-openssh"
]
},
"notes": "This is a placeholder! Please install 'git-with-openssh' or 'win32-openssh' instead!"
}
I implemented item 6. above in a proof-of-concept in #2431 . Both install and uninstall work, but we should really kick the tires before merging it in.
If I can add my 0.02PLN:
_change it to win32-openssh silently_
The fact that it's still in beta should not matter, I believe it's mature enough to be used.
Changing openssh to win32-openssh is my suggestion. It does not matter that it's still in beta, because Windows 10 RS4 has included it as a built-in tool. This is a good enough reason.
I added an rsync-via-git.json to #2431 to show how we can easily install other apps inside the git app's directory. Initial testing is encouraging.
There is also the PuTTY way, using plink and Pageant:
$Env:GIT_SSH=~\scoop\apps\putty\current\plink.exe[email protected]:<username>/<repo>.gitBut another problem is, win32-openssh isn't a good choice for those users who don't have elevated permission, since it is implemented as an OS service, restricted users cannot install its services.
Most helpful comment
If I can add my 0.02PLN:
_change it to win32-openssh silently_
The fact that it's still in beta should not matter, I believe it's mature enough to be used.