<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Korean Home-brew on the Web</title>
	<link>http://webstandards.or.kr/2007/03/17/korean-home-brew-on-the-web/</link>
	<description>The standard evangelism group for universial access and trust of web in Korea</description>
	<pubDate>Fri, 18 May 2012 04:10:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Channy Yun</title>
		<link>http://webstandards.or.kr/2007/03/17/korean-home-brew-on-the-web/#comment-30465</link>
		<pubDate>Sun, 18 Mar 2007 19:15:34 +0000</pubDate>
		<guid>http://webstandards.or.kr/2007/03/17/korean-home-brew-on-the-web/#comment-30465</guid>
					<description>Crowder, Thanks for your considerations.

In Korea, there is the law of digital signature and it didn't force technical specification. But, National Intelligence Service (aka CIA in US) and Financial Supervisory Service compel highly-coupled security system. Now it's not only SEED problem. Fortunately the lawsuit of Open Web rouses public opinion and government is aware of a matter of grave concern. Maybe alternatives such as Java applet will be offered in short-term.

Also I think there is two solutions in long term 1) changing loosely-coupled security system for users to choose their security level. 2) standardization of web signing process. Most of countries tend to have their own law of digital signature and CA system.</description>
		<content:encoded><![CDATA[<p>Crowder, Thanks for your considerations.</p>
<p>In Korea, there is the law of digital signature and it didn&#8217;t force technical specification. But, National Intelligence Service (aka CIA in US) and Financial Supervisory Service compel highly-coupled security system. Now it&#8217;s not only SEED problem. Fortunately the lawsuit of Open Web rouses public opinion and government is aware of a matter of grave concern. Maybe alternatives such as Java applet will be offered in short-term.</p>
<p>Also I think there is two solutions in long term 1) changing loosely-coupled security system for users to choose their security level. 2) standardization of web signing process. Most of countries tend to have their own law of digital signature and CA system.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: crowder</title>
		<link>http://webstandards.or.kr/2007/03/17/korean-home-brew-on-the-web/#comment-30099</link>
		<pubDate>Sun, 18 Mar 2007 03:15:22 +0000</pubDate>
		<guid>http://webstandards.or.kr/2007/03/17/korean-home-brew-on-the-web/#comment-30099</guid>
					<description>I have been obsessed with this ever since I read Gen Kanai's "Cost of Monoculture" article.  Thank you so much for a more precise technical analysis of the situation.  Given the issues that this is causing with Vista alone, is it possible that there will be political movement on this anytime soon?  Moving away from SEED as quickly as possible seems the only way to resolve what must be an economically hobbling situation like this.  I was talking to Vlad as he was exploring these bank-sites and installing the various "required" controlled and was literally flabbergasted at the promiscuity requested of users (-especially- as they are about to engage in online commerce!!).

It seems that once the policy here is addressed at the government level, banks and online commerce sites would want to switch as quickly as possible to a standards-based security model (for the convenience of their users, even if the browser-monopoly issue and the security hazards were ignored).  Is there any movement on this at any level of Korean government?</description>
		<content:encoded><![CDATA[<p>I have been obsessed with this ever since I read Gen Kanai&#8217;s &#8220;Cost of Monoculture&#8221; article.  Thank you so much for a more precise technical analysis of the situation.  Given the issues that this is causing with Vista alone, is it possible that there will be political movement on this anytime soon?  Moving away from SEED as quickly as possible seems the only way to resolve what must be an economically hobbling situation like this.  I was talking to Vlad as he was exploring these bank-sites and installing the various &#8220;required&#8221; controlled and was literally flabbergasted at the promiscuity requested of users (-especially- as they are about to engage in online commerce!!).</p>
<p>It seems that once the policy here is addressed at the government level, banks and online commerce sites would want to switch as quickly as possible to a standards-based security model (for the convenience of their users, even if the browser-monopoly issue and the security hazards were ignored).  Is there any movement on this at any level of Korean government?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Kelly Clowers</title>
		<link>http://webstandards.or.kr/2007/03/17/korean-home-brew-on-the-web/#comment-29867</link>
		<pubDate>Sat, 17 Mar 2007 16:54:28 +0000</pubDate>
		<guid>http://webstandards.or.kr/2007/03/17/korean-home-brew-on-the-web/#comment-29867</guid>
					<description>Thanks for this interesting post. I have been curious about the Korean ActiveX security system since I first heard about it, and this post clearly explains just how the system works (or doesn't work, as the case may be if you don't like lock-in ;-)</description>
		<content:encoded><![CDATA[<p>Thanks for this interesting post. I have been curious about the Korean ActiveX security system since I first heard about it, and this post clearly explains just how the system works (or doesn&#8217;t work, as the case may be if you don&#8217;t like lock-in <img src='http://webstandards.or.kr/en/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

