Re:More Than 1M Google Accounts Breached by Gooligan
by burkaman on Wednesday November 30, 2016 @12:01PM
(#13072374)
You definitely can't win, but those two complaints are not mutually exclusive. Instead of locking down apps to solve the first problem, in theory Microsoft could have redesigned Windows to make third party executables less of a risk. Obviously that's harder, but it's not hypocritical to make both those statements.
[ Parent
| on HN ]
Re:More Than 1M Google Accounts Breached by Gooligan
by tdkl on Wednesday November 30, 2016 @12:22PM
(#13072609)
I'm not exactly a fan of those, but I think MS is already doing that with UWP, which apps weren't exactly greeted with rejoice.
Re:More Than 1M Google Accounts Breached by Gooligan
by mtgx on Wednesday November 30, 2016 @12:45PM
(#13072819)
UWP apps can't be run outside of the MS store. So that's the lock-in he was talking about. It would be nice if Microsoft enabled "mini-VMs" for legacy x86 apps at least.
That way it could shoot two birds with one stone - make x86 apps a little slower and more resource intensive, and thus give both users and developers a reason to switch to UWP, while at the same time it would also make legacy x86 apps vastly more secure.
Re:More Than 1M Google Accounts Breached by Gooligan
by tdkl on Wednesday November 30, 2016 @12:59PM
(#13072959)
I think you can sideload them since 1607 (or even 1511?), there's a developer switch in new Control panel for that.
Re:More Than 1M Google Accounts Breached by Gooligan
by amyjess on Wednesday November 30, 2016 @03:50PM
(#13074568)
Windows 10 allows you to turn on sideloading. Going through the Windows Store is no longer a requirement.
Re:More Than 1M Google Accounts Breached by Gooligan
by pawadu on Thursday December 01, 2016 @08:01AM
(#13079059)
but then again, how is that different from android of today?
Re:More Than 1M Google Accounts Breached by Gooligan
by slrz on Wednesday November 30, 2016 @01:07PM
(#13073049)
The problem with that is that you can't tell programmatically if a potentially risky action is performed by a program acting as the user's agent or by a program acting on behalf of some malicious fuckwit.
You can just forbid it, sure, but then you're reducing the usefulness of your platform.