Parallels & Bootcamp - supress password request?
Parallels & Bootcamp - supress password request?
Author
Discussion

The Dude

Original Poster:

6,546 posts

278 months

Monday 9th July 2007
quotequote all
Anyone know how to stop Parallels from asking for my password (twice) when starting and stopping XP from my Bootcamp partition? From reading, it's the system that asks for your password as it unmounts and mounts your Bootcamp partition when Parallels access it but I can't find out out to suppress the request.

cyberface

12,214 posts

288 months

Monday 9th July 2007
quotequote all
Even if you're running as an admin user in OS X, you're still not root, so certain operations have to be run via sudo (as it should be, for OS X to be secure at any level).

Parallels does tricky stuff pulling the CPUs in and out of privileged mode. This requires root privilege, you'd not want any user pulling this sort of shite.

If you've already authenticated for sudo within the last 30 seconds or so, you won't get asked again, however this is unlikely unless you're doing a load of odd terminal stuff outside a root shell.

The two ways of suppressing Parallels asking for passwords are both completely insecure and IMO dangerous unless you *really* know what you're doing, and even then experienced sysadmins still make mistakes.

The first way is simply to log into your OS X box as root. Firstly you'll need to enable the root account, which is disabled for interactive login as default on OS X. If you don't know how to do this, I'm not telling you because I'm in a responsible mood, and if you run your OS X box GUI as root, sooner or later you're going to destroy your system. As I said, even experienced UNIX sysadmins occasionally up when logged in as root...

The second way is to hack into the scripts Parallels runs that try to run as root, and try to setuid root the script / binary. This may or may not be possible, and it will require you to get root shell access anyway.

If you go for the first option, then FFS choose a serious, hardcore root password... I don't know your level of expertise, but if this post sounds like gibberish then I respectfully suggest you put up with the password prompts, and choose a tricky password, and ensure the OS X firewall is ON at all times... there's a reason why OS X is one of the safest, least virus/worm-prone systems out there at the moment.

I have this horrible premonition that all these people running Windows alongside OS X will compromise OS X security via Windows vulnerabilities - running Parallels network with the NAT option is the best bet, bridged networking opens your Windows instance up to anything (again, a reason to use the OS X firewall)...

The Dude

Original Poster:

6,546 posts

278 months

Monday 9th July 2007
quotequote all
cyberface said:
Even if you're running as an admin user in OS X, you're still not root, so certain operations have to be run via sudo (as it should be, for OS X to be secure at any level).

Parallels does tricky stuff pulling the CPUs in and out of privileged mode. This requires root privilege, you'd not want any user pulling this sort of shite.

If you've already authenticated for sudo within the last 30 seconds or so, you won't get asked again, however this is unlikely unless you're doing a load of odd terminal stuff outside a root shell.

The two ways of suppressing Parallels asking for passwords are both completely insecure and IMO dangerous unless you *really* know what you're doing, and even then experienced sysadmins still make mistakes.

The first way is simply to log into your OS X box as root. Firstly you'll need to enable the root account, which is disabled for interactive login as default on OS X. If you don't know how to do this, I'm not telling you because I'm in a responsible mood, and if you run your OS X box GUI as root, sooner or later you're going to destroy your system. As I said, even experienced UNIX sysadmins occasionally up when logged in as root...

The second way is to hack into the scripts Parallels runs that try to run as root, and try to setuid root the script / binary. This may or may not be possible, and it will require you to get root shell access anyway.

If you go for the first option, then FFS choose a serious, hardcore root password... I don't know your level of expertise, but if this post sounds like gibberish then I respectfully suggest you put up with the password prompts, and choose a tricky password, and ensure the OS X firewall is ON at all times... there's a reason why OS X is one of the safest, least virus/worm-prone systems out there at the moment.

I have this horrible premonition that all these people running Windows alongside OS X will compromise OS X security via Windows vulnerabilities - running Parallels network with the NAT option is the best bet, bridged networking opens your Windows instance up to anything (again, a reason to use the OS X firewall)...
Great reply, thanks thumbup

None of it is gibberish but I'm not bothered enough by it (having to enter the passwords) to start messing with the root account, as you quite rightly warned. I just wondered (hoped) there'd be a simple (safe) way around it. I don't use XP enough anyway - only really have it because some of our server apps (MS Outlook Web Access etc) just don't run too pretty on Mac/Firefox...


cyberface

12,214 posts

288 months

Monday 9th July 2007
quotequote all
No worries. FWIW the US iPhone users are reporting that OWA works well and properly on the iPhone... so perhaps try Safari for Outlook web access. One of the iPhone users commenting on this was a Microsoft employee, so this isn't rampant Apple fanboyism...