Linked by Thom Holwerda on Fri 29th Jan 2010 16:26 UTC
Permalink for comment 406732
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2007-11-23
privilege separation = user account privileges [i.e administrator, limited user account, etc].
I also used to run on limited access user account and there were - in fact - problems with many applications, but again - it was MS fault in the first place!
here's the scheme:
1. MS designs its OS with user accounts, but no real privilege separation [i.e "do whatever you want, get the files from other accounts without giving a password] - Win95/98/NT/2k maybe?
2. MS again designs its OS with user accounts [crippled implementation - it makes YOU an admin by default] - WinXP 'Vanilla'
3. MS once again designs its OS with user accounts [now it's slightly better - "as it always should"] - WinXP Home / SP3 maybe?
4. MS changes the scheme: the previous one + UAC = more problems, more hell and inclarity. Devs are just *confused* ... - Vista / Win7
Of course I'm not talking about more advanced server versions, 'cause this is another thing. It's jus good.
But they couldn't even design their own software to work well on their own desktop OS, which is freaking hilarious!
Regards, Teknoenie