In the quest for higher and higher levels of security, management wants all bases coverd.
For instance, with the SSHD (daemon, to accept SSH connections from a remote machine), you have a config file that governs the behavior of the daemon, including MACs, etc.
For the SSH (client, to SSH "from" the ESXi server to some other remote machine), there is no configuration file, as delivered, to govern the client's behavior.
I'm wondering whether or not this version of OpenSSH that's included w/ESXi 5, requires that the client rely on the settings in the sshd_config. That is definitely not the case with "all" other OpenSSH installs that I am familiar with. There is always a ssh_config file AND an sshd_config file.
Or is it required that an ssh_config (client) file be created by the SA? Or is there "some" other means, IE: each user has to have an ssh_config (or .ssh_config, etc) file in their home directory?
So, in my case, the file "ssh_config" was not created during the install. Is it supposed to exist? Is it required? Can it be created and populated with Keyword and Keyword_Value pairs? Or is it just not required, not used, and not possible to use even if it is created in "/etc/ssh" (or anywhere else) by the SA?
ESXi is just plain and simple, an extremely, poorly documented, platform. Regardless of the fact that it is deemed a hypervisor by the vendor, the public at large, does not see it this way. Honestly, I've seen Radio Shack Color Computer 2 documentation that was light years ahead of what VMware has for ESXi5. And it especially doesn't help that Busybox is not documented by (at least) some online man pages. I understand the need for a small footprint, but that doesn't excuse the lack of a centralized, online, documentation repository. This lab/sandbox project I'm working has really left a bad taste for me. So much so, I'm already on record at my aerospace firm as giving vSphere the thumbs-down.
Anyway, thanks for any useful info you might have to offer.
