And then an infobar would show up (only in the first time) and tell them they can be relieved since they are secure again? ;) Sounds like an appropriate Google joke.
☆PhistucK On Fri, Dec 11, 2009 at 21:40, Steve VanDeBogart <[email protected]>wrote: > [from right address] > > On Fri, Dec 11, 2009 at 11:37 AM, Steve VanDeBogart <[email protected]>wrote: > >> >> >> On Fri, Dec 11, 2009 at 11:23 AM, Scott Hess <[email protected]> wrote: >> >>> >>> [[And now I'm waiting for someone to suggest the >>> --no-really-no-sandbox-i-like-being-insecure flag to suppress the >>> dialog :-).]] >>> >> >> Instead of telling people to use --no-sandbox on the blog, we could tell >> them to use a new flag, --disable-sandbox-until MM/DD/YYYY. It could limit >> the maximum amount of time the sandbox was disabled, to say two weeks. >> After that, the sandbox would automatically be reenabled. >> >> There should still be some kind of notification that the user is running >> with the sandbox disabled, but people that ignore it or forget about it will >> get converted back to a secure configuration in a reasonable amount of time. >> >> -- >> Steve >> > > -- > Chromium Developers mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev > -- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
