Recommended Posts

Adobe adds Flash sandboxing to Firefox

Hackers bypass it in 3, 2?

Adobe has released beta code for sandboxing its heavily hacked Flash code within Firefox, in a similar fashion to the Chrome security protections added to its Reader software and Google?s Chrome browser.

?Sandboxing technology has proven very effective in protecting users by increasing the cost and complexity of authoring effective exploits,? said Peleus Uhley, senior security researcher for Adobe in a blog post.

?For example, since its launch in November 2010, we have not seen a single successful exploit in the wild against Adobe Reader X. We hope to see similar results with the Flash Player sandbox for Firefox once the final version is released later this year.?

Adobe used elements of the sandboxing technology Google had built into Chrome for its Reader code, after a string of attacks against the popular Flash platform. The technology was released on November 2010 ? and promptly broken less than two months later by a Google engineer, although Adobe said this didn't count as it couldn't be done remotely. The code has also been added to Chrome, and Adobe promised other browsers would get similar protections.

The code will work with Firefox 4.0 or later versions running on Windows 7 or Vista. More details will be given in Uhley?s talk at the CanSecWest security conference in Vancouver, British Columbia, early next month.

Source: The Register

It's sad that Adobe has to do it since they know Mozilla never will.

What makes you think Mozilla wouldn't implement such a thing? I'd say Adobe need to do it themselves because Flash is a mess when it comes to security at this point.

What makes you think Mozilla wouldn't implement such a thing? I'd say Adobe need to do it themselves because Flash is a mess when it comes to security at this point.

It depends on how you implement the sandboxing, the mode Windows offers would break Flash and Java (Which is why Mozilla haven't implemented it). Google seems to have written their own sandboxing code which is why it works with Flash (because it's designed to simply, it allows it to break out of the sandbox when needed, while an OS provided sandbox would be stricter, etc.)

Sad that people still feel they have to use Flash. Thankfully pretty much every place I care in the slightest about has already switched away.

It's sad that people feel that they don't have to use Flash to avoid the clusterf*** of web standards and growing disparity between browsers and the fact that it gives us things you would have never had on the web. The ignorance among people is astounding. But I guess people will hate when they are being told to hate. No way around it.

It's sad that people feel that they don't have to use Flash to avoid the clusterf*** of web standards and growing disparity between browsers and the fact that it gives us things you would have never had on the web. The ignorance among people is astounding. But I guess people will hate when they are being told to hate. No way around it.

But, installing Flash always was the disparity. IMO, had Flash begun like Adobe Air (that is, a download and run anywhere piece of external software), it wouldn't have taken such a hit when Apple decided not to support it. It was the fact that Jobs said it couldn't run on iOS that made everyone else say, "oh, maybe we don't really need Flash." On the other hand, had it been a stand alone application that didn't require browser buy in, it could have taken a huge lead in early mobile development by porting Air over to iOS and Android (and anything else).

growing disparity between browsers

Huh? I know this is going a bit off topic, but the disparity has almost entirely been between IE and [the others] for about ten years. Since IE is catching up with the others, I really fail to see a 'growing' disparity. Sure there's differences between Webkit and Gecko for example (and there's some concern in CSS circles about that), but they're not so extreme as pretty much [everything] to IE6/7.

Adobe Flash is rock solid now. It outperforms IE9 HTML5 h264 performance on netbooks by my testing.

Huh? I know this is going a bit off topic, but the disparity has almost entirely been between IE and [the others] for about ten years. Since IE is catching up with the others, I really fail to see a 'growing' disparity. Sure there's differences between Webkit and Gecko for example (and there's some concern in CSS circles about that), but they're not so extreme as pretty much [everything] to IE6/7.

Everyone is adapting to Webkit now.

Adobe Flash is rock solid now. It outperforms IE9 HTML5 h264 performance on netbooks by my testing.

Everyone is adapting to Webkit now.

Who is everyone? Google and Apple.. you still have disparity between Google's Chrome and Apple's Safari in how they support CSS3 features (for example Google will support CSS3 regions and some Adobe proposed CSS3 additions while Apple added some Safari specific webkit transforms that allow you to get hardware accelerated effects that only work on Safari). Naturally, Firefox, Opera and IE do not use Webkit and have completely different ways of dealing with CSS and even DOM in some cases.

We have never been further away from unified browser because every browser maker has their own interests and politics and want to rule the web.

But I do agree with you, Flash is by far, today, years ahead of anything HTML5 offers and has quickly trumped the HTML5 video/h.264 performance it briefly lost to HTML5 but with Flash you have huge interactivity support via coding on top of the video layer, plus good DRM for commercial videos and so many other things. This is only for videos mind you.

I just hope that Adobe disables, sooner than later, right click on the Flash player as I guarantee all the hate mongering people will not even know what's flash and what's HTML if that was the case today.

This topic is now closed to further replies.
  • Posts

    • Yup, that's a doozy right there 😄
    • It's a bundle of tools created by a variety of people, so things can go wrong sometimes. It's a great addition to Windows, and I use a lot of the tools on a daily basis. Also, it's still a 0.**** release so quick updates are to be expected 😉
    • Oh, I did. And it's even worse than I was hoping! Besides a lot of techno-babble jargon (yes I understand 100% of it but it's still all just techno-babble) there's 2 key points that make me super-weary about even considering testing this out. -- By default, after installation, a relay is automatically set up, so you do not need to care about that. * Non-chatmail apps use email servers as a long-term message archive while chatmail clients use email servers for ephemeral instant message relay. * Supporting the full variety of classic email setups would require considerable development and maintenance efforts, and complicate making chatmail-based messaging more resilient, reliable and fast. -- Basically, the end-user device is the 'server' (relay) so there is NO ARCHIVING whatsoever because every message is necessarily ephemeral. Great for techno-paranoia (and for illicit activities preferring no tracks to cover) but terrible for everybody else. It's also ironically contradictory to engineering principles of redundancies besides the transport layers due to the explicit absence of any persistent storage. Instead of 'classic email address' retaining multi-GB messaging archives on its server, now every device must retain 100% of those storage demands. (Email messages were originally meant to be short correspondences, not the multi-MB attachments boondoggle that now exists with unlimited spam engines flooding every potential recipient.) Any device swap or reset (or loss) makes the entire message history go bye-bye forever... lest there's an off-device auto-archival "relay" mechanism that's really a separate server that holds onto all transported messages (an email server) that utilizes 'chatmail email address' identities (like an email server) and its own persistent storage archive (like an email server). But... this solution is hoping to exist alongside real-world email address identities (based on the email server relay pathway) but simply render messages in chat thread format in an ephemeral manner (with contents being encrypted, and messages auto-expiring) ... In the end, it's a chat app/experience for the Web3/P2P-at-all-costs zealots. (I have accts on all sorts of federated web3 services so I understand the technical and non-technical alike.) For any practical users, however, it's just another service to download/install, register, cross-share id cards/qr codes, but know that there's no history/archive whatsoever (by design) so no account/message recovery whatsoever... update the device, install a bummed update patch, or dare upgrade your device... all history, poof, gone. Ya gotta start everything over again like they're a brand new person.
    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!