<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: HTML5 security issues</title>
	<atom:link href="http://www.epanorama.net/blog/2013/08/01/html5-security-issues/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2013/08/01/html5-security-issues/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Thu, 23 Apr 2026 22:07:48 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: anon</title>
		<link>https://www.epanorama.net/blog/2013/08/01/html5-security-issues/comment-page-1/#comment-1372738</link>
		<dc:creator><![CDATA[anon]]></dc:creator>
		<pubDate>Wed, 08 Apr 2015 13:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=20550#comment-1372738</guid>
		<description><![CDATA[what is interesting and has perhaps been overlooked is that both cloud computing and html5 seem to have evolved on parralel paths. this is perhps no coincidence as both have huge security implcations both as seperate technologies and in combination with each other. take into consideraton that there has been heavy lobying for EME a form of DRM which allows the big boys to extend html5 and bybass the othewrwise open standard, it also means that the ability to inspect code will be thwarted in some cases thus making vulnerabilities harder to find, in addition this renders the &quot;rights!holders, those making use of EME/drm in the html codebase more likely to be open to accusation of being the progenitors of malicious code.]]></description>
		<content:encoded><![CDATA[<p>what is interesting and has perhaps been overlooked is that both cloud computing and html5 seem to have evolved on parralel paths. this is perhps no coincidence as both have huge security implcations both as seperate technologies and in combination with each other. take into consideraton that there has been heavy lobying for EME a form of DRM which allows the big boys to extend html5 and bybass the othewrwise open standard, it also means that the ability to inspect code will be thwarted in some cases thus making vulnerabilities harder to find, in addition this renders the &#8220;rights!holders, those making use of EME/drm in the html codebase more likely to be open to accusation of being the progenitors of malicious code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
