MSYS2-packages: SSH failing to find config and identities in user home

Description / Steps to reproduce the issue

SSH is unable to load identities and config stored in the usual ~/.ssh directory at all for me. Changing ~/.ssh/config is making no difference even when not using tokens in the path and instead using the system username. When running ssh-keygen it expands the default directory to //.ssh/, and for a few other commands it’s pointing up to /.ssh/ where I can confirm the expected modifications to e.g. known_hosts are happening. Some stat calls into looking around, it seems to be caused by some update after 2022-09-05 (creation and modification dates listed for stat ~/.ssh/known_hosts{,.old}) and it took me until now to notice because I’m only now setting up a new host for which I needed new keys (the others are local network hosts that take password auth)

Expected behavior

the SSH family of tools working from ~/.ssh/

Actual behavior

the same tools modifying files in the msys root directory.

Running ssh -G . to dump the config lists one notable entry - ~ is being considered an escape char. I wonder if that causes issues… Considering it’s checking the wrong directory, these are the defaults for the current package version. ssh_-G.log

Verification

• I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)

Windows Version

MSYS_NT-10.0-19045

Are you willing to submit a PR?

If I can figure out why things break, sure