5 ms·
Microsoft could fix the root problem for classic Windows applications (majority are WinAPI based applications). All apps should run by default in a sandbox cont
by frik 11y ago
Microsoft could fix the root problem for classic Windows applications (majority are WinAPI based applications). All apps should run by default in a sandbox container, then no Antivirus product would be needed (see Android, iOS, OSX). Windows would need more fine control permissions UI to like iOS9/Android6 so that only certain applications can access e.g. your picture folder. Windows already supports shims and shadow path/registry retranslation (used in IE and in the backward compatibility layer) - all what is missing is basically an end user GUI. Also executing applications under a different user should get easier, a common Unix security measure that is near impossible for normal users using Windows (except for whitelisted Microsoft Office applications).
- hirsin 11y ago> Also executing applications under a different user should get easier I'm curious - are you looking for something more command-line oriented or GUI-driven? I have no idea how to do it via command-line, but shift-right-click on an icon will give you the Run As Different User option. This may also not satisfy your needs - it only works for some users (i.e. you can't do Run As DefApps)
- frik 11y agoLike Android, iOS, OSX (or with Sandboxie on Windows) - new applications should start in a sandbox by default. The shift-right-click menu offers different entries depending on where desktop icon come from (the .lnk file is stored either in \Public\ or the users desktop directory). The run as different user is only shown if the lnk is stored in the "public" desktop.
- Quiark 11y agoYou can use the runas command to run something as a different user. Or one of the sysinternals utilities. Haven't used it much personally though.