On Thu, Aug 6, 2009 at 10:16 AM, Miguel F Mascarenhas Sousa Filipe < miguel.fil...@gmail.com> wrote:
> Hi, > > On Thu, Aug 6, 2009 at 6:08 PM, Jeremy Orlow <jor...@chromium.org> wrote: > >> Yoav everyone on this thread is a Chromium developer and almost everyone >> posting in this thread (not me) are some of the top developers working on >> Chrome and many of them have spent a good deal of time working on sandbox >> related issues. >> All of us have a healthy disrespect for the "impossible" and would >> definitely like to see plugin's sandboxed by default, but it's a very >> difficult problem. We're working hard on many fronts like making more stuff >> possible without plugins (HTML 5), new technologies (NaCl), etc to change >> the status quo. >> > > Sorry to intrude, but can you explain what NaCl are you talking ? > Is it this one: http://nacl.cr.yp.to/ > I was talking about this one: http://code.google.com/p/nativeclient/ > <http://nacl.cr.yp.to/> > And what kind of work/use is being thought for NaCl + chromium. > I'm asking this because I've looked at NaCl recently and seems very > interesting.. > > kind regards, > > > > >> >> I know it doesn't mean much to you, but I've met and/or worked with many >> of the developers that reached the conclusion that sandboxing plugins isn't >> practical (at least by default) and I can say that they're not only some of >> the smartest developers I've ever met, but that the decision was also >> painful to them. >> >> If you wanted to help, patches would be great. But I think it'd also be >> helpful if you turned it on and filed bugs when you hit compat issues. >> >> I'm not sure there's much else to say on the topic... >> >> J >> >> >> On Thu, Aug 6, 2009 at 9:50 AM, Adam Barth <aba...@chromium.org> wrote: >> >>> >>> I don't really understand why you find Alex's message so frustrating. >>> We'd love to make --safe-plugins the default. One road to getting >>> there is having more people use the option and find the >>> incompatibilities. We'd certainly welcome patches that improve it's >>> compatibility. If we can make it work well enough, then we can turn >>> it on by default and everyone wins. >>> >>> Adam >>> >>> >>> On Thu, Aug 6, 2009 at 9:46 AM, yoav >>> zilberberg<yoav.zilberb...@gmail.com> wrote: >>> > Alex, let me get it, are you part of the chrome team ? i don't recall >>> > accusing anyone from chrome >>> > but i do recall not liking your reply, so just let me know if you are >>> part >>> > of the devs of chrome please.... >>> > i will be honest, if you are, then i think it is time for me to move to >>> a >>> > different browser, if you are not >>> > then don't decide if i accuse the chrome team or not, let them tell me, >>> and >>> > like i said >>> > i would remove myself in a second and with no hard feelings >>> > >>> >>> >>> >> >> >> >> > > > -- > Miguel Sousa Filipe > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
