Recent Features
| |||||||||||||
Sandboxed file accessSandboxed file accessPosted Sep 5, 2012 1:36 UTC (Wed) by geofft (subscriber, #59789)In reply to: Sandboxed file access by reddit Parent article: Ubuntu's new app developer upload process proposal Most of this is covered -- and attacked -- in the literature, and in particular the literature of years and years ago. People have been caring about secure windowing for ages; the first reference off the top of my head is this 20-plus year-old paper about extending X, but I'm sure you can find older things if you try. Most of the attacks are along the lines of tricking the users, or relying on them not to pay attention. Randomized titlebar colors seem like they will work about as well as secure pictures for anti-phishing for banks, i.e., not actually that well. Also, you should look at Qubes, from the previous post, which is actually attempting to be a secure desktop OS.
(Log in to post comments)
Sandboxed file access Posted Sep 5, 2012 9:33 UTC (Wed) by khim (subscriber, #9252) [Link] Also, you should look at Qubes, from the previous post, which is actually attempting to be a secure desktop OS. Well, it tries to build a secure desktop OS, but, as usual, in the end it'll create secure server OS. On desktop the biggest problem is Dancing pigs problem. MacOS and Ubuntu are trying to solve it by making it inconviniet for the end-user to give full access to the homedir (you need to select files one-after-another to give them to the application). This works: user will send comple of dozen of his (or her) files to-god-knows-where but s/he'll quickly become bored and will just close the program without obtaining these valuable dancing pigs. Not an ideal outcome but much better then what we have today. If you'll add the ability to request the user to open a directory and get access to all children developers will start asking for the access to
|
|||||||||||||