ssh-config | SSH config parser and stringifier

So for windows, I see the default ssh client config supposed to be placed at C:\Users\Admin\.ssh\config and I use the same, also I am the Admin user.

I added the following ssh client side config:

I followed the following steps from https://docs.ceph.com/en/latest/cephadm/install/ to setup a ceph cluster on Centos 8.1

I've created public and private keys, and added the public key to the Bitbucket repository.

These private/public key pair is available in the .ssh folder of the user account I hope to clone to.

Attempting to clone with SSH produces a connection refused:

This lead me to believe that either the Bitbucket project/server is not configured for ssh, or maybe this is a firewall/port issue for my companies network. However, port 7999 and port 22 are open.

This lead me to investigate other means of cloning with ssh, but over http as described here (just in case if port 22 or 7999 was blocked): https://support.atlassian.com/bitbucket-cloud/docs/troubleshoot-ssh-issues/ 

To do this I modified my ssh config as follows:

Doing this allowed me to atleast establish a connection with bitbucket, but it acts as if the request was bad:

This lead me to believe that maybe i signed the cert incorrectly so I attempted a flavor of this: https://unix.stackexchange.com/questions/503851/how-to-generate-a-certificate-file-which-to-be-used-with-ssh-config 

To add the certificatefile provided in the ssh config. It sounded like I would need to add that public key of the private key used to sign the user key (that generated the certificate). However, I won't have access to the private key for the cert available on the bitbucket server.

Separately, I was able to grab the public cert from altssh.bitbucket.di2e.net:443 and I did try using this, but still got a bad request... This probably doesn't make sense to use since this is in PEM format, but I figured it was worth a try.. 

I'd like to use multiple Git server accounts (with any of GitHub, GitLab, BitBubket etc.).

The accounts are distinguished by their email addresses, name1@email1.com and name2@email2.org and git is setup to use these addresses in the relevant repositories

The following constraints apply to the 'change-account workflow':

1. Without touching/changing SSH config files (e.g. ~/.ssh/config, etc.) when repositories or servers are added/removed/changed.
2. Without requiring SSH agent running i.e. no ssh-add ....
3. Without changing environment variables.
4. Without changing the git clone instruction.
5. Isolate the SSH keys used with git away from other SSH keys.
6. Use the same 'change-account workflow' across all private and public repositories.
7. The 'change-account workflow' is a one (1) step/command.
8. The 'change-account workflow' is one (1) time per repository (i.e. not each time you move into work on the repository).

The initial repository setup (which is also one time activity) can involve more than one step. Any conventions/assumptions are acceptable as long as they don't break the constraints.

These are responses that do not satisfy the constraints.
They generally require changes to ~/.ssh/config and/or involve the SSH agent daemon:

1. handle-multiple-git-account
2. using-multiple-git-accounts
3. multiple-git-accounts-and-ssh-key
4. multiple-github-accounts-ssh-config
5. multiple-git-users-on-same-machine
6. multiple-github-accounts-with-git-in-windows
7. git-multiple-accounts-and-repository-problems
8. ssh-config-to-access-multiple-repo-not-working
9. multiple-github-accounts-on-the-same-computer
10. can-i-specify-multiple-users-for-myself-in-gitconfig
11. setting-up-ssh-config-file-for-multiple-codebase-accounts
12. how-can-i-push-git-with-multiple-accounts-on-one-machine
13. multiple-github-accounts-what-values-for-host-in-ssh-config
14. how-to-configure-multiple-github-accounts-on-your-computer
15. ssh-config-with-multiple-keys-for-multiple-gitlab-user-accounts
16. github-multiple-accounts-permission-to-personalusername-reponame-git-denied-to