Skip to main content

Understanding VMware Infrastructure Client Connectivity

Ed has some good tips. Last time I spoke to Ed, I got to understand that he's on to a lot more things such as writing a book and some toolkit. Mike Hoesing has beaten him to it there since his book on Virtualization Security is already up there on Amazon. I am looking forward to Ed's book as well though.

Anyways, like I said, last when I spoke to Ed was about pushing the virtualization security initiative here in the EMEA. I have spoken to several little and bigger players, including our own large team ("our" as in my employer) of some 500+ security experts,who are doing lots RA's for firms across the globe.

Anyways here's Haletky's article:

The roles and permissions within the VI Client do not necessarily map to users and groups within the service console or management appliance. Roles and permissions are quite a bit different actually and do not always map one to one.

When you directly connect the VI Client to a VMware ESX or VMware ESXi host you will use a local username and password to log in. But after that, all actions depend on your roles and permissions within the VI Client. The VI Client does not run any command as the user to which you logged in. Instead it runs those commands you are entitled to run as the root user. Since the root user is also the super user, it can run any command available to the system. This translation happens automatically as the vmware-hostd daemon runs as the root user.

The same happens when you log in using the VI Client to VMware vCenter Server. VMware vCenter Server uses the vpxuser to contact the vmware-hostd daemon which in turn runs all the necessary commands as the root user.

For a direct connection, a user must exist on the VMware ESX or VMware ESXi host, but for an indirect connection, no user must exist on the hosts. This implies that when you use vCenter there is no real need to manage multiple user account systems. Unfortunately, in reality you often have to have users on your VMware ESX and VMware ESXi hosts to perform support actions.



Source
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Virtualization: GlassHouse hopes to cash in with its IPO!

GlassHouse Technologies Inc. on Tuesday registered to raise as much as $100 million in an initial public offering that, despite the company's financial losses, could prove a hit with investors drawn to its focus on "virtualization" technology. The Framingham, Mass., company offers consulting services for companies that use virtualization software to improve the performance of corporate servers and cut costs in their data centers. GlassHouse also provides Internet-based data storage. "Software-as-a-service," or SaaS, companies and vendors of virtualization products have proved popular among investors in recent years as corporate customers seek alternatives to conventional packaged software. GlassHouse, with roots in both sectors, will test the strength of that interest, said Peter Falvey, managing director with Boston investment bank Revolution Partners. "It will be a bit of a bell weather," he says. "It's not as though it's the 15th SaaS m...
Post a Comment
Read more