Ian,
Anyway I thank you for your careful consideration and encouragement of
another activities.
Basically web signature must be implemented by browser venders because of an
example of XKMS's fail that Anders indicated. So we have to consider how to
do is cost effective and I think form
able to get the
Korean e-goverment signature spec since it is secret!
On Tue, 31 Oct 2006, Channy Yun wrote:
Korean mechanism is same with general pki's. Its structure has been
followed by pki standards and browser user-interface for certificates.
The different things has own 128bit
to add digital
signature function as like crypto.signText action in HTML 5. If others want
to make spec. of more secure than browser based digital signature in HTML5,
it can go to IETF or other body.
Please reconsider that.
Channy
On Thu, Jul 31, 2008 at 7:19 PM, Channy Yun [EMAIL PROTECTED] wrote
Anders,
As you said, we may not get sufficient informations to standardize
digital signature. But, in case of Korea, I'll sufficiently give them.
The spec. and interface are almost standardized by governmental rules
to all vendors.
In Korea, the own cryptic algorithm has been encouraged, so
On 10/30/06, Anders Rundgren [EMAIL PROTECTED] wrote:
Michael(tm) Smith wrote:
It is equally interesting that W3C intends to start a new browser
authentication WG but have excluded digital signatures and key
provisioning from the charter in spite of the fact that about 10M
people today have
Dear WHATWG,
As you know, Bon Echo Alpha3 starts to support client-side session and
persistent storage in Web Application 1.0 spec made by WHATWG. But, as
following sample code of 4.9.1 doesn't work in Bon Echo Alpha 3.
p
You have viewed this page
span id=countan untold number of/span
Dear whatwg folks,
At last W3C announced a charter of Web Application W/G and Rich Web
Client Activity Proposal. As you know, this activitiy will be started
in September, 2005. According to charter, they included standardzation
of all RIA technology (XUL, XAML, MXML, XBL and APIs) and combination
