<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:osnews="http://osnews.com/rss2#">
	<channel>
		<title>OSNews: </title>
		<link>http://www.osnews.com/story/21793/Gazelle_Applying_Operating_System_Concepts_to_the_Browser</link>
		<description>Exploring the Future of Computing</description>
		<language>en-us</language>
		<copyright>Copyright 2001-2009, David Adams</copyright>
		<webMaster>adam+nospam@osnews.com</webMaster>
		<lastBuildDate>Thu, 26 Nov 2009 11:51:48 GMT</lastBuildDate>
		<image>
			<url>http://www.osnews.com/images/osnews.gif</url>
			<title>OSNews.com</title>
			<link>http://www.osnews.com</link>
		</image>
		<item>
			<title>Cool.</title>
			<link>http://osnews.com/thread?372172</link>
			<guid isPermaLink="true">http://osnews.com/thread?372172</guid>
			<description>Now when the browser is having problems drawing a page, it'll show the Blue Screen of Death, and I'll have to reboot.</description>
			<pubDate>Tue, 07 Jul 2009 23:32:00 GMT</pubDate>
			<author>donotreply@osnews.com (gehersh)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>not sure ..</title>
			<link>http://osnews.com/thread?372181</link>
			<guid isPermaLink="true">http://osnews.com/thread?372181</guid>
			<description>not sure basing your security on domains is the right idea .. there is no real reason that abc.com is different from def.com ... its just a DNS domain name and that doesn't mean they are different or the same originator. this isn't that revolutionary.<br />
 <br />
its a bit like a Windows anti-virus application treating files differently depending on their drive letter (C:, D:, etc). in reality it doesn't mean anything. they could even be on the same drive!<br />
<br />
 they'd be better off sorting out buffer overflows and more bread and butter security weaknesses ...Edited 2009-07-08 00:34 UTC</description>
			<pubDate>Wed, 08 Jul 2009 00:32:00 GMT</pubDate>
			<author>donotreply@osnews.com (project_2501)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: Cool.</title>
			<link>http://osnews.com/thread?372182</link>
			<guid isPermaLink="true">http://osnews.com/thread?372182</guid>
			<description>How is that a new thing?<br />
<br />
I'd call this a BSOD. Wouldn't you agree? <img src="/images/emo/wink.gif" alt=";)" /> <br />
<a href="http://img219.imageshack.us/img219/144/bsod.png" rel="nofollow">http://img219.imageshack.us/img219/144/bsod.png</a></description>
			<pubDate>Wed, 08 Jul 2009 00:36:00 GMT</pubDate>
			<author>donotreply@osnews.com (drstorm)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: not sure ..</title>
			<link>http://osnews.com/thread?372196</link>
			<guid isPermaLink="true">http://osnews.com/thread?372196</guid>
			<description>That's not what people generally exploit on the web.  It's far more common to see these Cross-Site Scripting attacks against the design of the web applications than against the browser code.<br />
<br />
It's the same reason why people go after applications running on Windows much more than after the OS itself: it's a lot easier and likely just as lucrative.</description>
			<pubDate>Wed, 08 Jul 2009 03:12:00 GMT</pubDate>
			<author>donotreply@osnews.com (PlatformAgnostic)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>A solution for a problem no one cares about</title>
			<link>http://osnews.com/thread?372205</link>
			<guid isPermaLink="true">http://osnews.com/thread?372205</guid>
			<description>Maybe it is that this will be practical/needed in the future as the web heads for a more application-like platform, but really, is anyone concerned at all about the problems Gazelle is trying to address?</description>
			<pubDate>Wed, 08 Jul 2009 04:57:00 GMT</pubDate>
			<author>donotreply@osnews.com (elmimmo)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE[2]: Cool.</title>
			<link>http://osnews.com/thread?372210</link>
			<guid isPermaLink="true">http://osnews.com/thread?372210</guid>
			<description>Well, you see, it's not really blue... <img src="/images/emo/tongue.gif" alt=";)" /></description>
			<pubDate>Wed, 08 Jul 2009 06:11:00 GMT</pubDate>
			<author>donotreply@osnews.com (l3v1)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE[3]: Cool.</title>
			<link>http://osnews.com/thread?372242</link>
			<guid isPermaLink="true">http://osnews.com/thread?372242</guid>
			<description>Well, it is kinda... blueish.<br />
And it's definitely a screen of Death. Just look at the icon. It's dead. <img src="/images/emo/tongue.gif" alt=";)" /></description>
			<pubDate>Wed, 08 Jul 2009 10:12:00 GMT</pubDate>
			<author>donotreply@osnews.com (drstorm)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: not sure ..</title>
			<link>http://osnews.com/thread?372356</link>
			<guid isPermaLink="true">http://osnews.com/thread?372356</guid>
			<description>One very common and insidious (has happened with google and amazon, among others) attack is Cross Site Request Forgeries (or CSRF)<br />
<br />
The idea is this: you go to your bank, and check the &quot;keep me signed in&quot; checkbox (which any bank worth their salt would NOT have, but this is an example). That site puts an authentication cookie in your browser. Next time you go to the site, it checks the cookie, and doesn't bother asking for username/password, but just forwards you a long to the next screen.<br />
<br />
Now, I have a site (or use an XSS attack against a site you use), and I do an AJAX request that mimics a form submission to transfer money to my account. The site receives the request, checks for authentication, since it is the browser making the request it finds the cookie, and just lets it through.<br />
<br />
These kinds of exploits are very difficult to avoid, the only thing you can really do is generate an authentication tolken on every page, and then checking for it on the next request from that session.</description>
			<pubDate>Wed, 08 Jul 2009 21:42:00 GMT</pubDate>
			<author>donotreply@osnews.com (google_ninja)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: A solution for a problem no one cares about</title>
			<link>http://osnews.com/thread?372357</link>
			<guid isPermaLink="true">http://osnews.com/thread?372357</guid>
			<description>Yes, pretty much everyone is. The browser is an application that executes arbitrary code off the internet, and that millions of people enter sensitive information into.</description>
			<pubDate>Wed, 08 Jul 2009 21:47:00 GMT</pubDate>
			<author>donotreply@osnews.com (google_ninja)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>Neat</title>
			<link>http://osnews.com/thread?372358</link>
			<guid isPermaLink="true">http://osnews.com/thread?372358</guid>
			<description>This sort of reminds me of a microkernel OS archetecture.</description>
			<pubDate>Wed, 08 Jul 2009 21:48:00 GMT</pubDate>
			<author>donotreply@osnews.com (google_ninja)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: A solution for a problem no one cares about</title>
			<link>http://osnews.com/thread?373046</link>
			<guid isPermaLink="true">http://osnews.com/thread?373046</guid>
			<description><div class="cquote">Maybe it is that this will be practical/needed in the future as the web heads for a more application-like platform, but really, is anyone concerned at all about the problems Gazelle is trying to address? </div><br />
<br />
Very much so. Never mind &quot;in the future&quot; - the web is already well on the way to an application-like platform, and has been for several years. And if you look through recent Firefox release notes, you'll notice that a substantial proportion of the bugs fixed in the 3.0.x series were security bugs of this kind.</description>
			<pubDate>Sun, 12 Jul 2009 22:49:00 GMT</pubDate>
			<author>donotreply@osnews.com (Delgarde)</author>
			<category>Comments</category>
		</item>
	</channel>
</rss>
