Issue 3965: The sandbox doesn't allow checking attributes on non-existant files in allowed directories http://code.google.com/p/chromium/issues/detail?id=3965
New issue report by [EMAIL PROTECTED]: Chrome Version : 0.3.155.0 What steps will reproduce the problem? 1. Run Chromium with --gears-in-renderer 2. Start the Gears unit test server 3. Go to http://localhost:8001/tester/gui.html?LocalServer 4. Note that all attempts to remove a store fail when the permissions database is updated. This is due to the inability of sqlite to verify that its journal file has been deleted, which is done by checking the attributes on the file. What is the expected result? Attempts to check the attributes on the file do not give an access denied error. What happens instead? Attempts to check the attributes on the file give an access denied error. The only way I could get around this was by explicitly allowing access to the journal file, which will not work for all databases, since we don't know all possible names ahead of time. Issue attributes: Status: Unconfirmed Owner: [EMAIL PROTECTED] Labels: Type-Bug Pri-2 OS-All Area-Misc -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
