Deleteing the guest login user in XP Home....little help pls!!

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Den

Member
Jan 11, 2000
168
0
0
Er, you recomend disabling it even though the text you just posted says not to? I am confused...
 

stash

Diamond Member
Jun 22, 2000
5,468
0
0
D'oh...i think I assumed they meant delete in the article.

I still think MS's advice is a baaaad idea, unless the machine is never connected to the outside world.
 

c0rv1d43

Senior member
Oct 1, 2001
737
0
0
Well, if their assertion that the presence of the Guest account is necessary to the proper functioning of shares I'd say it might be more deleterious to security to disable the account. Since they don't specify exactly what they mean when they talk about malfunctioning shares I guess we don't really know whether that could constitute a security issue. It obviously can constitute a threat to the proper operation of the OS, though.

They're not saying that the account has to be active or "on", after all. By default it's not. Assuming that the account name is changed, and that it's prohibited from both local and remote logon, I'm not sure it would matter so much even if a would-be interloper could figure out a way to turn it on. After all, if you had to go through that much trouble to access that account, wouldn't you shoot for an account with better access? The danger of Guest accounts has always been that sysadmins overlooked the Guest account thinking that it was too "weak" to be a danger. If they didn't rename the account and also allowed local and / or remote login it was a toe-in-the-door for would-be invaders.

Sounds almost as though they're saying that this account behaves as a sort of policy template for the system, doesn't it?

- Collin
 

stash

Diamond Member
Jun 22, 2000
5,468
0
0
My impression was that they were referring to setting up shares on a peer-to-peer network. The easiest way to do it is obviously to enable the guest account.

However I suspect that you are right that it serves as a template of some kind. MS has never allowed the guest account to be disabled...they must have some reason for requiring such an obvious target for a breech to stay on the system.

Whatever their reason, I still say that people should keep it disabled (even if they have a peer-to-peer network--its more of hassle to create accounts on every machine, but more secure), give it a good password and change the name of the account.