W3C home > Mailing lists > Public > public-webcrypto@w3.org > September 2012

Re: adding SEED cryptography algorithm

From: Ryan Sleevi <sleevi@google.com>
Date: Fri, 31 Aug 2012 17:13:52 -0700
Message-ID: <CACvaWvZ9k9WZvLd1XcuHsrjkB=kujaSUvhkWC590QWyFQDViaA@mail.gmail.com>
To: Mountie Lee <mountie.lee@mw2.or.kr>
Cc: Web Cryptography Working Group <public-webcrypto@w3.org>
On Fri, Aug 31, 2012 at 4:59 PM, Mountie Lee <mountie.lee@mw2.or.kr> wrote:

> Hi.
> WebCrypto Korea Community is preparing to suggest "SEED" algorithm to be
> added to API spec.
> "SEED" is block ciphers symmetric encryption algorithm registered in
> international standard as ISO/IEC 1803303, IETF RFC 4269
> I will update the algorithm details in next mails.
> regards
> mountie.
> =======================================
> PayGate Inc.
> for Korea, Japan, China, and the World
> Thanks for bringing this up, Mountie.

It does seem reasonable to at least spec out for implementations that will
support SEED. As you mention, it's defined in RFC 4269.

While supported by PKCS#11, it's not defined as a (standard) algorithm by
CNG [1] or CryptoAPI [2][3], nor is it supported by SecTransform API on OS
X [4].

This means that I think you'll find it very hard to be implemented across
user agents using 'standard' OS APIs. But having it normatively spec'd I
think is fine. Perhaps you'd be willing to take an ACTION item to help
provide state-of-the-art implementation across common user agent platforms
(including mobile) regarding the support of SEED, since I anticipate user
agents will be deferring to platform APIs to perform crypto.


Received on Saturday, 1 September 2012 00:14:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:13 UTC