IETF Logo Mail Archive

Re: [OAUTH-WG] proposal for signatures

Nat Sakimura <sakimura@gmail.com> Tue, 27 July 2010 06:58 UTC

Return-Path: <sakimura@gmail.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44C023A6907 for <oauth@core3.amsl.com>; Mon, 26 Jul 2010 23:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_41=0.6]
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 bgRkurTdEg9y for <oauth@core3.amsl.com>; Mon, 26 Jul 2010 23:58:23 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 1F45E3A68D7 for <oauth@ietf.org>; Mon, 26 Jul 2010 23:58:23 -0700 (PDT)
Received: by iwn38 with SMTP id 38so3745393iwn.31 for <oauth@ietf.org>; Mon, 26 Jul 2010 23:58:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=sIGOOiRXDtnaN6tWKwCKzBdsIG7kmXmkj49Uk5ZLLek=; b=DwU8zd3fx2b++eBGaTYshkVcXVxLJL2WhiYgIAvVYOcDEPx7FV6/4Gmxui3xoTvWXb RDn9k7U3+smpKt9SvjEkbX35H/64j5UluOkzW2xh5hMGkeFU7nIoeUlfsttWiwTZ4Oxi W4Cy6ag4w4X/Pb9j2sKSCV3j3j35OBAoJ8U3A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fHdQIXt4Nl0XBMHUe7zh+XZ8XIFraiA72PejwrP5ZnkrIxInv+vxYTBSTW9oBKPlOc fpB+40gD2YVU3t6++pz2VIwYfWaHJzUWzsy+ZoVmTuSwXwVG/MfIqb7gbilg5K5ced/G cVkLGxNz2AO3Otib2i5hOOUgNviqzGzzGq1no=
MIME-Version: 1.0
Received: by 10.231.203.15 with SMTP id fg15mr9259858ibb.187.1280213924762; Mon, 26 Jul 2010 23:58:44 -0700 (PDT)
Received: by 10.231.158.67 with HTTP; Mon, 26 Jul 2010 23:58:44 -0700 (PDT)
In-Reply-To: <AANLkTimMM2h-5x4DoAMIBST4fUrnlrfWGvKZ0AzxMGX_@mail.gmail.com>
References: <AANLkTingCgO-o3XRZbxYoD8U2rRTO-EgWcfg2hBlbQHm@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E11264272EBE@WSMSG3153V.srv.dir.telstra.com> <AANLkTimMM2h-5x4DoAMIBST4fUrnlrfWGvKZ0AzxMGX_@mail.gmail.com>
Date: Tue, 27 Jul 2010 15:58:44 +0900
Message-ID: <AANLkTi=CH70svVPAt1AJ3MPLhmDWAV4jYodr0PQEVgxb@mail.gmail.com>
From: Nat Sakimura <sakimura@gmail.com>
To: Ben Laurie <benl@google.com>, Dirk Balfanz <balfanz@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] proposal for signatures
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 06:58:24 -0000

If we were using PKCS#7 for certs, then why not PKCS#7 the payload as well?

(No - I am not proposing to do it. Doing so with AES-128,192,256 is
prohibitive in some language such as PHP, but just as a point of
discussion to close this.)

On Tue, Jun 22, 2010 at 6:33 PM, Ben Laurie <benl@google.com> wrote:
> On 22 June 2010 02:40, Manger, James H <James.H.Manger@team.telstra.com> wrote:
>> Nat and Ben,
>>
>>
>>
>>>>> In addition to Ben's questions, I have another. For X.509, you seem to
>>
>>>>> be using DER. How do you express the entire certificate chain using
>>
>>>>> DER?
>>
>>>>> (With PEM, you can just concatenate ... )
>>
>>>>
>>
>>>> With DER you can concatenate, too, of course. There's also PKCS#n (for
>>
>>>> some value of n which I forget ... 12?) which allows bundling of cert
>>
>>>> chains.
>>
>>>
>>
>>> That's PKCS#12, I suppose. I had under an impression that PKCS#12 includes
>>> the
>>
>>> private key, though.
>>
>>
>>
>>
>>
>> A *.p7c file can be used to hold any number of certificates. It is a
>> BER-encoded PKCS#7 value, now known as Cryptographic Message Syntax (CMS)
>> standard [RFC 5652]. It is the ASN.1 syntax used for S/MIME signed email. If
>> you only want to send certificates, just leaving out the
>> content-to-be-signed, and the signatures.
>
> Ah, thanks, I thought there was something less kludgey than PKCS#12.
>
>>
>>
>>
>> Such a file can hold any number of certificates, including public-key
>> certificates, attribute certificates, or other certificate formats.
>>
>> It can also hold CRLs and other revocation information (including OCSP
>> responses as per draft-turner-additional-cms-ri-choices).
>>
>>
>>
>> CMS/PKCS#7 is better for this purpose than PKCS#12.
>>
>>
>>
>> --
>>
>> James Manger
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>



-- 
Nat Sakimura (=nat)
http://www.sakimura.org/en/
http://twitter.com/_nat_en

v2.35.0 | Report a Bug | By Email | System Status