W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2006

[whatwg] Browser Signature Standards Proposal

From: Channy Yun <channy@gmail.com>
Date: Wed, 1 Nov 2006 17:22:15 +0900
Message-ID: <3586624e0611010022kcac5aa1ld5921705d2d31067@mail.gmail.com>
Dear Alexey,

Using HTTPS with a client-side certificate doesn't support digital
signature.The digital signature is same with the signing or stamp of
contract in real world. Many governments encourage to add digital
signature to transactional data (form data). It legally assures data
and transactions signed(added digital signature) by user's
certificates.

Channy

On 11/1/06, Alexey Feldgendler <alexey at feldgendler.ru> wrote:
> On Wed, 01 Nov 2006 00:24:08 +0600, Channy Yun <channy at creation.net> wrote:
>
> > As I said in other thread, I think digital signature must be
> > standardized for secure and legal assurance of form data and I respect
> > your issuing and great jobs. But, we can simply think this issue in
> > range of this group. Most of forms directly go to web server via
> > urlencoded. If some indicators are given, browsers can execute signing
> > process.
> >
> > For example,
> >
> > <form name="sendmoney" action="/send.cgi" signed="signed">
> > <input type="text" name="dollars" value="3.00">
> > <input type="text" name="account" values="1234567890">
> > <input type="submt" value="Sending Money!">
> > </form>
>
> What benefit does this provide over simply using HTTPS with a client-side certificate?
>
>
> --
> Alexey Feldgendler <alexey at feldgendler.ru>
> [ICQ: 115226275] http://feldgendler.livejournal.com
>
Received on Wednesday, 1 November 2006 00:22:15 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:49 UTC