Re: draft-ietf-dnsext-dnssec-gost
Sean Turner <turners@ieca.com> Fri, 12 February 2010 00:02 UTC
Return-Path: <turners@ieca.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E5EB3A7572 for <ietf@core3.amsl.com>; Thu, 11 Feb 2010 16:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level:
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e3mccVxVEsW1 for <ietf@core3.amsl.com>; Thu, 11 Feb 2010 16:02:33 -0800 (PST)
Received: from smtp106.biz.mail.re2.yahoo.com (smtp106.biz.mail.re2.yahoo.com [206.190.52.175]) by core3.amsl.com (Postfix) with SMTP id 376633A7289 for <ietf@ietf.org>; Thu, 11 Feb 2010 16:02:33 -0800 (PST)
Received: (qmail 95905 invoked from network); 12 Feb 2010 00:03:46 -0000
Received: from pool-96-241-6-27.washdc.east.verizon.net (turners@96.241.6.27 with plain) by smtp106.biz.mail.re2.yahoo.com with SMTP; 11 Feb 2010 16:03:45 -0800 PST
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
X-YMail-OSG: c37D37YVM1kFNnXOVorg.dUXhArcKMTLcW5uwl6jmUib5oOBxXNH5AqLjQjcb7SFm80Y2EVYtT9DtF4kXqmmAfZtxR6Q547pWAsAGgnI_iXhOTMjw40QKo.lgCIzSsttrjde0BUW4uH4MM_wWUoiSJ2h73.vXvEzMG5K3Uxtwy26_IAZ3X4cnNeV80N9FVQSAhvEs94ozumeq.nUvtiC_5s.Sbr7R.0LhCIPK7pX_YTuuihUSvh6KUMT3NMyMs6EoWTt3iPnerIOQCdiv19U0o8vZ.O0K_twjilwQCtO.kUXomwCJWfnGXbzSkdvTYBeCQtkxLk1PLjBdolRWNP_0WQwcC3CCIbBQKPxfOpBg43SOYKfsmdSOMxFXgVvC1uSeyq60QXLuUCdo58A2XNAd8t9pAbgFZMOax6YrFKrqlYIOjkzmLdmREOKEboGwj5e95Fu0xacNiiVjXs.GHPjrZEUk0U.s0ag6y499YsQywggCStJ_14ZVLrfV_tTVlx8pzw6d9wpS4tnfJxGosPoPzgld9GJvJY-
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4B749AE1.2050000@ieca.com>
Date: Thu, 11 Feb 2010 19:03:45 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Michael Dillon <wavetossed@googlemail.com>
Subject: Re: draft-ietf-dnsext-dnssec-gost
References: <p06240806c799d87e7406@128.89.89.170> <201002112243.o1BMhvn1003940@fs4113.wdf.sap.corp> <877585b01002111539i7dc6f6ccl8381289c69ac5fa6@mail.gmail.com>
In-Reply-To: <877585b01002111539i7dc6f6ccl8381289c69ac5fa6@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2010 00:02:34 -0000
Michael Dillon wrote: >> One of the problems with GOST is its lack of availability of >> documentation/specification and the meaning, purpose and >> characteristics of algorithm parameters. > > A bit of Googling turned up this <http://vsegost.com/Catalog/96/9658.shtml> > with scanned GIFs of ГОСТ Р34.10-1994. There is a link to the other one, > ГОСТ Р34.10-2001 on that page as well. This does seem to document > the parameters. > > Is the real problem the lack of English language documentation? > If so, I'm sure that the people who would like to use these algorithms > could arrange for translations of the two documents, and perhaps even > make that an individual submission as an Internet draft. English translation, I don't believe, is the problem. The following drafts are the English translations of the [GOST3410] and [GOST3411] references: http://tools.ietf.org/html/draft-dolmatov-cryptocom-gost341194-07 http://tools.ietf.org/html/draft-dolmatov-cryptocom-gost34102001-08 http://tools.ietf.org/html/draft-dolmatov-cryptocom-gost2814789-06 >> Whether and how much the -1994 version is >> deprecated is also a complete mystery. > > That may be explained by its use in card payment systems. As you may > know if you follow the news, a Cambridge team has just found a HUGE hole > in the UK's chip and pin payment system, but a subtext of that announcement > is that other weaknesses documented in previous years still have not been fixed. > Signature algorithms used in payment systems get embedded in all kinds > of devices, and software systems, making it hard to deprecate stuff fast. > > --Michael Dillon > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf
- Re: draft-ietf-dnsext-dnssec-gost Paul Hoffman
- Re: draft-ietf-dnsext-dnssec-gost Olafur Gudmundsson
- draft-ietf-dnsext-dnssec-gost Stephen Kent
- Re: draft-ietf-dnsext-dnssec-gost Andrew Sullivan
- Re: draft-ietf-dnsext-dnssec-gost Paul Hoffman
- Re: draft-ietf-dnsext-dnssec-gost Richard L. Barnes
- Re: draft-ietf-dnsext-dnssec-gost Martin Rex
- Re: draft-ietf-dnsext-dnssec-gost Michael Dillon
- Re: draft-ietf-dnsext-dnssec-gost Sean Turner
- Re: draft-ietf-dnsext-dnssec-gost Martin Rex
- Re: draft-ietf-dnsext-dnssec-gost Sean Turner
- Re: draft-ietf-dnsext-dnssec-gost Basil Dolmatov
- Re: draft-ietf-dnsext-dnssec-gost Basil Dolmatov
- Re: draft-ietf-dnsext-dnssec-gost Stephen Farrell
- Re: draft-ietf-dnsext-dnssec-gost Andrew Sullivan
- Re: draft-ietf-dnsext-dnssec-gost Stephen Kent
- Re: draft-ietf-dnsext-dnssec-gost Martin Rex
- Re: draft-ietf-dnsext-dnssec-gost David Conrad
- Re: draft-ietf-dnsext-dnssec-gost Edward Lewis
- Re: draft-ietf-dnsext-dnssec-gost Sean Turner
- Re: draft-ietf-dnsext-dnssec-gost Olafur Gudmundsson
- Re: draft-ietf-dnsext-dnssec-gost Martin Rex
- Re: draft-ietf-dnsext-dnssec-gost Basil Dolmatov
- Re: draft-ietf-dnsext-dnssec-gost Basil Dolmatov
- Re: draft-ietf-dnsext-dnssec-gost ned+ietf
- Re: draft-ietf-dnsext-dnssec-gost Martin Rex
- Re: draft-ietf-dnsext-dnssec-gost Stephen Kent
- Re: draft-ietf-dnsext-dnssec-gost Stephen Kent
- RE: draft-ietf-dnsext-dnssec-gost Rex, Martin
- Re: draft-ietf-dnsext-dnssec-gost Spencer Dawkins
- Re: draft-ietf-dnsext-dnssec-gost Martin Rex
- Re: draft-ietf-dnsext-dnssec-gost Mark Andrews
- Re: draft-ietf-dnsext-dnssec-gost Martin Rex
- Re: draft-ietf-dnsext-dnssec-gost Olafur Gudmundsson
- Re: draft-ietf-dnsext-dnssec-gost Olafur Gudmundsson
- Re: draft-ietf-dnsext-dnssec-gost Basil Dolmatov
- Re: draft-ietf-dnsext-dnssec-gost Andrew Sullivan
- Re: draft-ietf-dnsext-dnssec-gost Martin Rex
- Re: draft-ietf-dnsext-dnssec-gost Ran Atkinson
- Re: draft-ietf-dnsext-dnssec-gost Phillip Hallam-baker
- Re: draft-ietf-dnsext-dnssec-gost Phillip Hallam-baker
- Re: draft-ietf-dnsext-dnssec-gost Olafur Gudmundsson