...knowing all this, how does it get fixed? What is the proper way for MS to enforce UAC?
On Fri, Feb 6, 2009 at 11:58 AM, Andy McKnight <[email protected]>wrote: > > > 2009/2/6 Ureleet <[email protected]> > >> doesnt this work for other oses? > > > Windows is different in this respect. The number of Windows users who > don't know/care (or *want* to know) what goes on under the hood is *huge*. > As long as their current setup allows them to *do their job* then they're > not going to buy into any upgrade that risks breaking that. That's what's > important to them. > > The biggest driver behind upgrading a Windows OS isn't a new release, or > security improvements or a fancy GUI. It's hardware replacement. Even this > was/is stretched with XP with the extended shipment dates and various > downgrade options you can *still* get on new boxes. > > The only people that can really force app developers to change overnight* > and code for a new, secure Windows OS mostly don't care about it. That > leaves Microsoft to try and drip feed gradual change that improves the > situation without rocking the boat. > > *relatively. > > _______________________________________________ > Full-Disclosure - We believe in it. > Charter: http://lists.grok.org.uk/full-disclosure-charter.html > Hosted and sponsored by Secunia - http://secunia.com/ >
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
