From owner-ietf-openpgp@mail.imc.org Tue Jun 06 12:45:37 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnegT-0005Em-O2 for openpgp-archive@lists.ietf.org; Tue, 06 Jun 2006 12:45:37 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnegS-0008R1-5O for openpgp-archive@lists.ietf.org; Tue, 06 Jun 2006 12:45:37 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56G9tbl067462; Tue, 6 Jun 2006 09:09:55 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k56G9tCt067461; Tue, 6 Jun 2006 09:09:55 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from foobar.cs.jhu.edu (foobar.cs.jhu.edu [128.220.13.173]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56G9qGW067394 for ; Tue, 6 Jun 2006 09:09:55 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.hsd1.ma.comcast.net (walrus.hsd1.ma.comcast.net [24.60.132.70]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id k56G9jk05434 for ; Tue, 6 Jun 2006 12:09:45 -0400 Received: from grover.jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.hsd1.ma.comcast.net (8.13.6/8.13.6) with ESMTP id k56GEMBS020459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 6 Jun 2006 12:14:22 -0400 Received: from grover.jabberwocky.com (grover.jabberwocky.com [127.0.0.1]) by grover.jabberwocky.com (8.13.1/8.13.1) with ESMTP id k56G9ddC010875 for ; Tue, 6 Jun 2006 12:09:39 -0400 Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id k56G9d6p010874 for ietf-openpgp@imc.org; Tue, 6 Jun 2006 12:09:39 -0400 Date: Tue, 6 Jun 2006 12:09:39 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: DSA2 test material Message-ID: <20060606160939.GC28850@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.11 Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 I have put together some sample keys and signatures to help test DSA2 interoperability and posted the lot at http://www.jabberwocky.com/openpgp/dsa2.tar.gz Note that the current released version of GnuPG (1.4.3) can verify, but will not generate a DSA2 signature or key. The next version will allow generation of DSA2 keys if the --enable-dsa2 option is given (off by default to try and minimize the "Hey, neat, a bigger key. What do you mean most of the world can't verify my signatures?" factor). The readme file: This archive contains material to help verify interoperability to the OpenPGP DSA2 design as implemented in GnuPG. Keys are located in the keys directory. Included are: 1024 bits, 160 bit q size (i.e. regular old DSA) 2048 bits, 224 bit q size 3072 bits, 256 bit q size 7680 bits, 384 bit q size 15360 bits, 512 bit q size All secret keys have the passphrase "test". Note the inclusion of 7680/384 and 15360/512 keys. They're large, inconvenient and absurdly slow. GnuPG will accept any size key, but will not generate DSA keys over 3072 bits. I include these keys mainly for be-liberal-in-what-you-accept testing. There are are signatures issued by these keys in the sigs directory. The filenames indicate the key used to make the signature, and the number of bits of the hash. In the case of the 1024-bit DSA key (160-bit q size), there are 5 signatures using different hashes. This is to demonstrate hash truncation to fit in the 160-bit hash size of that key. File Key size Hash ---------------------- ---------- ------- dsa-1024-160-sign.gpg 1024 bits SHA-1 dsa-1024-224-sign.gpg 1024 bits SHA-224 (truncated to 160 bits) dsa-1024-256-sign.gpg 1024 bits SHA-256 (truncated to 160 bits) dsa-1024-384-sign.gpg 1024 bits SHA-384 (truncated to 160 bits) dsa-1024-512-sign.gpg 1024 bits SHA-512 (truncated to 160 bits) dsa-2048-224-sign.gpg 2048 bits SHA-224 dsa-3072-256-sign.gpg 3072 bits SHA-256 dsa-7680-384-sign.gpg 7680 bits SHA-384 dsa-15360-512-sign.gpg 15360 bits SHA-512 David From owner-ietf-openpgp@mail.imc.org Tue Jun 06 16:20:31 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fni2R-0001Uj-7Q for openpgp-archive@lists.ietf.org; Tue, 06 Jun 2006 16:20:31 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fni2R-0002Z6-50 for openpgp-archive@lists.ietf.org; Tue, 06 Jun 2006 16:20:31 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fni2I-00029y-PV for openpgp-archive@lists.ietf.org; Tue, 06 Jun 2006 16:20:25 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56JdxWM033628; Tue, 6 Jun 2006 12:39:59 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k56JdxAh033627; Tue, 6 Jun 2006 12:39:59 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.135]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56Jdwha033620 for ; Tue, 6 Jun 2006 12:39:58 -0700 (MST) (envelope-from vedaal@hush.com) Received: from smtp3.hushmail.com (localhost.hushmail.com [127.0.0.1]) by smtp3.hushmail.com (Postfix) with SMTP id ED9C9A3508 for ; Tue, 6 Jun 2006 12:39:56 -0700 (PDT) Received: from mailserver7.hushmail.com (mailserver7.hushmail.com [65.39.178.62]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Tue, 6 Jun 2006 12:39:54 -0700 (PDT) Received: by mailserver7.hushmail.com (Postfix, from userid 65534) id 96E0BDA827; Tue, 6 Jun 2006 12:39:54 -0700 (PDT) Date: Tue, 06 Jun 2006 15:39:54 -0400 To: Cc: Subject: Re: DSA2 test material From: Content-type: text/plain; charset="UTF-8" Message-Id: <20060606193954.96E0BDA827@mailserver7.hushmail.com> Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: -2.6 (--) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 On Tue, 06 Jun 2006 12:09:39 -0400 David Shaw wrote: >I have put together some sample keys and signatures to help test >DSA2 >interoperability and posted the lot at >http://www.jabberwocky.com/openpgp/dsa2.tar.gz > >Note that the current released version of GnuPG (1.4.3) can >verify, >but will not generate a DSA2 signature or key. tested them in gnupg (1.4.3 mingw32 on win2k pro) got a few error messages: all involving the '224' type was this meant to be tested in 1.4.3 ? here is the ouptut summary of gpg --version gpg (GnuPG) 1.4.3 Copyright (C) 2006 Free Software Foundation, Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the file COPYING for details. Home: V:/ Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA Cipher: IDEA (S1), 3DES (S2), CAST5 (S3), BLOWFISH (S4), AES (S7), AES192 (S8), AES256 (S9), TWOFISH (S10) Hash: MD5 (H1), SHA1 (H2), RIPEMD160 (H3), SHA256 (H8), SHA384 (H9), SHA512 (H10) Compression: Uncompressed (Z0), ZIP (Z1), ZLIB (Z2), BZIP2 (Z3) a hash of 224 is not listed so, not unexpectely, upon importing the key, since gnupg didn't recognize the 224 hash, it also didn't recognize the self-sig here are the gnupg error messages (using verbose verbose setting): [1] gpg: pub 2048D/41FBF40E 2006-05-26 gpg: key 41FBF40E: invalid self-signature on user ID "DSA-2048-224" gpg: key 41FBF40E: skipped user ID "DSA-2048-224" gpg: key 41FBF40E: no valid user IDs gpg: this may be caused by a missing self-signature gpg: Total number processed: 1 gpg: w/o user IDs: 1 File: V:\dsa2tf\DSA2-Tests\keys\DSA-2048-224.pub Time: 6/6/2006 2:37:52 PM (6/6/2006 6:37:52 PM UTC) [2] gpg: original file name='dsa-1024-224-sign' gpg: md_enable: algorithm 11 not available gpg: Signature made 5/27/2006 23:03:25 using DSA key ID 94D38E40 gpg: Can't check signature: unknown digest algorithm File: V:\dsa2tf\DSA2-Tests\sigs\dsa-1024-224-sign.gpg Time: 6/6/2006 2:47:01 PM (6/6/2006 6:47:01 PM UTC) [3] gpg: original file name='dsa-2048-224-sign' gpg: md_enable: algorithm 11 not available gpg: Signature made 5/27/2006 19:33:49 using DSA key ID 41FBF40E gpg: Can't check signature: unknown digest algorithm File: V:\dsa2tf\DSA2-Tests\sigs\dsa-2048-224-sign.gpg Time: 6/6/2006 3:04:25 PM (6/6/2006 7:04:25 PM UTC) vedaal Concerned about your privacy? Instantly send FREE secure email, no account required http://www.hushmail.com/send?l=480 Get the best prices on SSL certificates from Hushmail https://www.hushssl.com?l=485 From owner-ietf-openpgp@mail.imc.org Tue Jun 06 17:15:25 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnitY-0001hd-Rz for openpgp-archive@lists.ietf.org; Tue, 06 Jun 2006 17:15:24 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnitX-0001FI-1c for openpgp-archive@lists.ietf.org; Tue, 06 Jun 2006 17:15:24 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56Ke5Zb049635; Tue, 6 Jun 2006 13:40:05 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k56Ke5G5049634; Tue, 6 Jun 2006 13:40:05 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from foobar.cs.jhu.edu (foobar.cs.jhu.edu [128.220.13.173]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56Ke4du049626 for ; Tue, 6 Jun 2006 13:40:04 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.hsd1.ma.comcast.net (walrus.hsd1.ma.comcast.net [24.60.132.70]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id k56Ke3k07167 for ; Tue, 6 Jun 2006 16:40:03 -0400 Received: from grover.jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.hsd1.ma.comcast.net (8.13.6/8.13.6) with ESMTP id k56KifX0022431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 6 Jun 2006 16:44:41 -0400 Received: from grover.jabberwocky.com (grover.jabberwocky.com [127.0.0.1]) by grover.jabberwocky.com (8.13.1/8.13.1) with ESMTP id k56Kdvjh011479 for ; Tue, 6 Jun 2006 16:39:57 -0400 Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id k56Kdtt1011478 for ietf-openpgp@imc.org; Tue, 6 Jun 2006 16:39:55 -0400 Date: Tue, 6 Jun 2006 16:39:55 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: Re: DSA2 test material Message-ID: <20060606203955.GB11349@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org References: <20060606193954.96E0BDA827@mailserver7.hushmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060606193954.96E0BDA827@mailserver7.hushmail.com> OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.11 Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 On Tue, Jun 06, 2006 at 03:39:54PM -0400, vedaal@hush.com wrote: > > On Tue, 06 Jun 2006 12:09:39 -0400 David Shaw > wrote: > > >I have put together some sample keys and signatures to help test > >DSA2 > >interoperability and posted the lot at > >http://www.jabberwocky.com/openpgp/dsa2.tar.gz > > > >Note that the current released version of GnuPG (1.4.3) can > >verify, > >but will not generate a DSA2 signature or key. > > > tested them in gnupg (1.4.3 mingw32 on win2k pro) > > got a few error messages: > all involving the '224' type > > was this meant to be tested in 1.4.3 ? No. This is meant for people developing OpenPGP implementations other than GPG. David From owner-ietf-openpgp@mail.imc.org Wed Jun 07 09:32:12 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fny8q-0000eL-L8 for openpgp-archive@lists.ietf.org; Wed, 07 Jun 2006 09:32:12 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fny8p-00015Z-96 for openpgp-archive@lists.ietf.org; Wed, 07 Jun 2006 09:32:12 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57CiQxE023902; Wed, 7 Jun 2006 05:44:26 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k57CiQ4j023900; Wed, 7 Jun 2006 05:44:26 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from mail.ihtfp.org (MAIL.IHTFP.ORG [204.107.200.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57CiPJF023883 for ; Wed, 7 Jun 2006 05:44:26 -0700 (MST) (envelope-from warlord@MIT.EDU) Received: from cliodev.pgp.com (CLIODEV.IHTFP.ORG [204.107.200.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cliodev.ihtfp.com", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail.ihtfp.org (Postfix) with ESMTP id 2A7FEBD8393 for ; Wed, 7 Jun 2006 08:44:23 -0400 (EDT) Received: (from warlord@localhost) by cliodev.pgp.com (8.13.6/8.13.1/Submit) id k57CiHQl004324; Wed, 7 Jun 2006 08:44:17 -0400 From: Derek Atkins To: ietf-openpgp@imc.org Subject: Topic/Speaker requests for Montreal Date: Wed, 07 Jun 2006 08:44:17 -0400 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.1 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Hi, Montreal is just around the corner. What with 2440bis "done", it's time to get down to other projects. I've requested a 1-hour timeslot in Montreal so we can discuss other OpenPGP related topics. Now is the time to revive those drafts that we sidelined to get 2440bis out the door. Topics that have been brought to my attention (and that I recall at the moment): PFS Alternate Ciphers OpenPGP Mail Header IPsec If you've got a draft and want to present it, let me know how much time you want. If you'd got an idea that you'd like to present but no draft, let me know that, too. Thanks! -derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant From owner-ietf-openpgp@mail.imc.org Wed Jun 07 11:54:55 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo0Mx-0002Ji-D4 for openpgp-archive@lists.ietf.org; Wed, 07 Jun 2006 11:54:55 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo0Mv-000280-W8 for openpgp-archive@lists.ietf.org; Wed, 07 Jun 2006 11:54:55 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57FADDS066374; Wed, 7 Jun 2006 08:10:13 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k57FADWN066373; Wed, 7 Jun 2006 08:10:13 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.135]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57FACCA066367 for ; Wed, 7 Jun 2006 08:10:12 -0700 (MST) (envelope-from vedaal@hush.com) Received: from smtp3.hushmail.com (localhost.hushmail.com [127.0.0.1]) by smtp3.hushmail.com (Postfix) with SMTP id DEBC4A3491 for ; Wed, 7 Jun 2006 08:10:11 -0700 (PDT) Received: from mailserver8.hushmail.com (mailserver8.hushmail.com [65.39.178.61]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Wed, 7 Jun 2006 08:10:11 -0700 (PDT) Received: by mailserver8.hushmail.com (Postfix, from userid 65534) id 420BDDA82A; Wed, 7 Jun 2006 08:10:11 -0700 (PDT) Date: Wed, 07 Jun 2006 11:10:10 -0400 To: Cc: Subject: Re: Topic/Speaker requests for Montreal From: Content-type: text/plain; charset="UTF-8" Message-Id: <20060607151011.420BDDA82A@mailserver8.hushmail.com> Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.2 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 On Wed, 07 Jun 2006 08:44:17 -0400 Derek Atkins wrote: >Now is the time to revive those drafts that we sidelined to get >2440bis out the door. Topics that have been brought to my >attention >(and that I recall at the moment): > > PFS > Alternate Ciphers > OpenPGP Mail Header > IPsec would like to suggest/request the topic of 'Deniable Authentication' specifically, the Ian Brown - Adam Back proposed solution of a signature on the session key hashed with recipient's public key http://www.cs.ucl.ac.uk/staff/I.Brown/nts.htm as it would involve the addition of a new packet type, rather than changing any existing packets, it might not be as difficult to incorporate into open-pgp Thanks, vedaal Concerned about your privacy? Instantly send FREE secure email, no account required http://www.hushmail.com/send?l=480 Get the best prices on SSL certificates from Hushmail https://www.hushssl.com?l=485 From owner-ietf-openpgp@mail.imc.org Wed Jun 07 13:37:46 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo1yU-0007Bt-C3 for openpgp-archive@lists.ietf.org; Wed, 07 Jun 2006 13:37:46 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo1yR-00075I-V9 for openpgp-archive@lists.ietf.org; Wed, 07 Jun 2006 13:37:46 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57GjRhR099611; Wed, 7 Jun 2006 09:45:28 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k57GjRKt099610; Wed, 7 Jun 2006 09:45:27 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from mail.links.org (mail.links.org [217.155.92.109]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57GjQ0E099583 for ; Wed, 7 Jun 2006 09:45:27 -0700 (MST) (envelope-from ben@algroup.co.uk) Received: from [193.133.15.218] (localhost [127.0.0.1]) by mail.links.org (Postfix) with ESMTP id 321DD33C1C; Wed, 7 Jun 2006 17:45:25 +0100 (BST) Message-ID: <44870264.5010402@algroup.co.uk> Date: Wed, 07 Jun 2006 17:44:20 +0100 From: Ben Laurie User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: vedaal@hush.com CC: ietf-openpgp@imc.org Subject: Re: Topic/Speaker requests for Montreal References: <20060607151011.420BDDA82A@mailserver8.hushmail.com> In-Reply-To: <20060607151011.420BDDA82A@mailserver8.hushmail.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 vedaal@hush.com wrote: > > > On Wed, 07 Jun 2006 08:44:17 -0400 Derek Atkins > wrote: > >> Now is the time to revive those drafts that we sidelined to get >> 2440bis out the door. Topics that have been brought to my >> attention >> (and that I recall at the moment): >> >> PFS >> Alternate Ciphers >> OpenPGP Mail Header >> IPsec > > would like to suggest/request the topic of 'Deniable > Authentication' > > specifically, the Ian Brown - Adam Back proposed solution > of a signature on the session key hashed with recipient's public > key > > http://www.cs.ucl.ac.uk/staff/I.Brown/nts.htm Grrr, it uses the "non-repudiation" word. But, sounds like a good idea to me. -- http://www.apache-ssl.org/ben.html http://www.links.org/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff From owner-ietf-openpgp@mail.imc.org Fri Jun 09 09:07:14 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Foghm-0007jw-Rs for openpgp-archive@lists.ietf.org; Fri, 09 Jun 2006 09:07:14 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Foghl-0003hA-EK for openpgp-archive@lists.ietf.org; Fri, 09 Jun 2006 09:07:14 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k59Ca04r028170; Fri, 9 Jun 2006 05:36:00 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k59Ca0tu028169; Fri, 9 Jun 2006 05:36:00 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from mail.ihtfp.org (MAIL.IHTFP.ORG [204.107.200.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k59CZxNZ028153 for ; Fri, 9 Jun 2006 05:35:59 -0700 (MST) (envelope-from warlord@MIT.EDU) Received: from cliodev.pgp.com (CLIODEV.IHTFP.ORG [204.107.200.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cliodev.ihtfp.com", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail.ihtfp.org (Postfix) with ESMTP id B141EBD8393 for ; Fri, 9 Jun 2006 08:35:58 -0400 (EDT) Received: (from warlord@localhost) by cliodev.pgp.com (8.13.6/8.13.1/Submit) id k59CZwCl007503; Fri, 9 Jun 2006 08:35:58 -0400 From: Derek Atkins To: ietf-openpgp@imc.org Subject: (FWD) Internet-Drafts Submission Cutoff Dates for the 66th IETF Meeting in Montreal, Quebec, Canada Date: Fri, 09 Jun 2006 08:35:57 -0400 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.1 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 --=-=-= In case any of you are polishing up drafts for discussion in Montreal, the cutoff dates are coming quickly. Just a reminder from your friendly neighborhood working-group chair. -derek --=-=-= Content-Type: message/rfc822 Content-Disposition: inline To: ietf-announce@ietf.org From: ietf-secretariat@ietf.org Date: Fri, 09 Jun 2006 00:00:01 -0400 Subject: Internet-Drafts Submission Cutoff Dates for the 66th IETF Meeting in Montreal, Quebec, Canada Lines: 41 MIME-Version: 1.0 There are two (2) Internet-Draft cutoff dates for the 66th IETF Meeting in Montreal, Quebec, Canada: June 19th: Cutoff Date for Initial (i.e., version -00) Internet-Draft Submissions All initial Internet-Drafts (version -00) must be submitted by Monday, June 19th at 9:00 AM ET. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they can be processed or announced. The Secretariat would appreciate receiving WG Chair approval by Monday, June 12th at 9:00 AM ET. June 26th: Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft Submissions All revised Internet-Drafts (version -01 and higher) must be submitted by Monday, June 26th at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective cutoff dates will not be made available in the Internet-Drafts directory or announced until on or after Monday, July 10th at 9:00 AM ET, when Internet-Draft posting resumes. Please do not wait until the last minute to submit. Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 66th IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_dates_66.html. --=-=-= -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant --=-=-=-- From owner-ietf-openpgp@mail.imc.org Tue Jun 27 09:49:22 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvDwQ-0005gv-Gg for openpgp-archive@lists.ietf.org; Tue, 27 Jun 2006 09:49:22 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvDwP-0008Fv-2h for openpgp-archive@lists.ietf.org; Tue, 27 Jun 2006 09:49:22 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5RDLg4L083804; Tue, 27 Jun 2006 06:21:42 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k5RDLg4v083803; Tue, 27 Jun 2006 06:21:42 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from mail.ihtfp.org (MAIL.IHTFP.ORG [204.107.200.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5RDLeSV083785 for ; Tue, 27 Jun 2006 06:21:41 -0700 (MST) (envelope-from warlord@MIT.EDU) Received: from cliodev.pgp.com (CLIODEV.IHTFP.ORG [204.107.200.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cliodev.ihtfp.com", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail.ihtfp.org (Postfix) with ESMTP id 2B1F8BD844A for ; Tue, 27 Jun 2006 09:21:36 -0400 (EDT) Received: (from warlord@localhost) by cliodev.pgp.com (8.13.6/8.13.1/Submit) id k5RDLX8w008551; Tue, 27 Jun 2006 09:21:33 -0400 From: Derek Atkins To: ietf-openpgp@imc.org Subject: [Russ Housley] Fwd: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to Experimental RFC (draft-ietf-tls-openpgp-keys) Date: Tue, 27 Jun 2006 09:21:33 -0400 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.1 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a --=-=-= Hey, all. I'm forwarding this on from Russ, who specifically asked for OpenPGP participants to review this document. As this is an IETF Last Call, everyone should try to take a little time to make this this document fits into the 2440/2440bis model reasonably. Comments can be sent to me, to Russ, to the TLS list, or to the IETF list depending on how you feel. Note that if you send it to me, I assume you just want it anonymized and I'll forward it on without your name attached. Happy reading! -derek --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Message-Id: <7.0.0.16.2.20060626133837.07511268@vigilsec.com> Date: Mon, 26 Jun 2006 13:40:22 -0400 To: Derek Atkins From: Russ Housley Subject: Fwd: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to Experimental RFC (draft-ietf-tls-openpgp-keys) Lines: 29 MIME-Version: 1.0 Derek: It would be good to have some OpenPGP participants review this document. Russ >To: IETF-Announce >From: The IESG >Date: Mon, 26 Jun 2006 11:50:44 -0400 >Cc: tls@ietf.org >Subject: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to > Experimental RFC (draft-ietf-tls-openpgp-keys) > >The IESG has received a request from the Transport Layer Security WG to >consider the following document: > >- 'Using OpenPGP keys for TLS authentication ' > as an Experimental RFC > >The IESG plans to make a decision in the next few weeks, and solicits >final comments on this action. Please send any comments to the >iesg@ietf.org or ietf@ietf.org mailing lists by 2006-07-10. > >The file can be obtained via >http://www.ietf.org/internet-drafts/draft-ietf-tls-openpgp-keys-10.txt --=-=-= -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant --=-=-=-- From owner-ietf-openpgp@mail.imc.org Tue Jun 27 10:41:23 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvEkl-0007qE-4V for openpgp-archive@lists.ietf.org; Tue, 27 Jun 2006 10:41:23 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvEkj-0002lp-Pf for openpgp-archive@lists.ietf.org; Tue, 27 Jun 2006 10:41:23 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5REMVdj000933; Tue, 27 Jun 2006 07:22:31 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k5REMVWO000932; Tue, 27 Jun 2006 07:22:31 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [217.69.77.222]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5REMTJE000914 for ; Tue, 27 Jun 2006 07:22:29 -0700 (MST) (envelope-from wk@gnupg.org) Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.50 #1 (Debian)) id 1FvEaa-0000yS-LD for ; Tue, 27 Jun 2006 16:30:52 +0200 Received: from wk by localhost with local (Exim 4.62 #1 (Debian)) id 1FvENS-0007Vg-I3 for ; Tue, 27 Jun 2006 16:17:18 +0200 From: Werner Koch To: ietf-openpgp@imc.org Subject: Re: [Russ Housley] Fwd: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to Experimental RFC (draft-ietf-tls-openpgp-keys) References: Organisation: g10 Code GmbH OpenPGP: id=5B0358A2; url=finger:wk@g10code.com Date: Tue, 27 Jun 2006 16:17:18 +0200 In-Reply-To: (Derek Atkins's message of "Tue, 27 Jun 2006 09:21:33 -0400") Message-ID: <87bqsebs41.fsf@wheatstone.g10code.de> User-Agent: Gnus/5.110006 (No Gnus v0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Hi, I can't comment on TLS specific things but here are a few minor things: 1. Introduction [...] OpenPGP keys (sometimes called OpenPGP certificates), provide security services for electronic communications. They are widely deployed, especially in electronic mail applications, provide public key authentication services, allow distributed key management and can be used with a non hierarchical trust model called the "web of trust" [WOT]. Because OpenPGP does not define any trust model, a wording like ... and allows the use in non hierarchical trust models, for example the "Web of Trust"[WOT]. seems to better to me. [...] 2.3. Server Certificate [...] DHE_RSA RSA public key which can be used for signing. Shouldn't this say: "RSA public key which can be used for authentication"? Recall that OpenPGP features a key flag to indicate an authentication key (0x20). [...] 3. Security Considerations As with X.509 ASN.1 formatted keys, OpenPGP keys need specialized parsers. Care must be taken to make those parsers safe against maliciously modified keys, that could cause arbitrary code execution. That is superfluous as this is (or well, should) be standard programming practise. It is in no way special to TLS or OpenPGP. Salam-Shalom, Werner From owner-ietf-openpgp@mail.imc.org Tue Jun 27 12:29:38 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvGRW-0002vR-GA for openpgp-archive@lists.ietf.org; Tue, 27 Jun 2006 12:29:38 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvGRU-0005ar-VT for openpgp-archive@lists.ietf.org; Tue, 27 Jun 2006 12:29:38 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5RG2EKZ027906; Tue, 27 Jun 2006 09:02:14 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k5RG2Eu6027904; Tue, 27 Jun 2006 09:02:14 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from merrymeet.com (merrymeet.com [63.73.97.162]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5RG2DKR027894 for ; Tue, 27 Jun 2006 09:02:13 -0700 (MST) (envelope-from jon@callas.org) Received: from keys.merrymeet.com (keys.merrymeet.com [63.73.97.166]) (Authenticated sender: jon) by merrymeet.com (Postfix) with ESMTP id 363861AC655 for ; Tue, 27 Jun 2006 09:02:11 -0700 (PDT) Received: from [10.13.252.251] ([212.44.18.222]) by keys.merrymeet.com (PGP Universal service); Tue, 27 Jun 2006 09:02:11 -0700 X-PGP-Universal: processed; by keys.merrymeet.com on Tue, 27 Jun 2006 09:02:11 -0700 Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <87bqsebs41.fsf@wheatstone.g10code.de> References: <87bqsebs41.fsf@wheatstone.g10code.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jon Callas Subject: Re: [Russ Housley] Fwd: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to Experimental RFC (draft-ietf-tls-openpgp-keys) Date: Tue, 27 Jun 2006 09:02:03 -0700 To: OpenPGP X-Mailer: Apple Mail (2.750) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 On 27 Jun 2006, at 7:17 AM, Werner Koch wrote: > > Hi, > > I can't comment on TLS specific things but here are a few minor > things: > > 1. Introduction > > [...] > > OpenPGP keys (sometimes called OpenPGP certificates), provide > security services for electronic communications. They are widely > deployed, especially in electronic mail applications, provide > public > key authentication services, allow distributed key management > and can > be used with a non hierarchical trust model called the "web of > trust" > [WOT]. > > Because OpenPGP does not define any trust model, a wording like > > ... and allows the use in non hierarchical trust models, for > example the "Web of Trust"[WOT]. > > seems to better to me. > The important thing is that trust models are not part of OpenPGP. I think it should also say, "OpenPGP certificates (often called OpenPGP keys), ..." for reasons I'll state more fully after my comments on Werner's comments. > > [...] > > 2.3. Server Certificate > > [...] > > DHE_RSA RSA public key which can be used for > signing. > > Shouldn't this say: "RSA public key which can be used for > authentication"? Recall that OpenPGP features a key flag to indicate > an authentication key (0x20). > Yes, it should. > > [...] > > 3. Security Considerations > > As with X.509 ASN.1 formatted keys, OpenPGP keys need specialized > parsers. Care must be taken to make those parsers safe against > maliciously modified keys, that could cause arbitrary code > execution. > > That is superfluous as this is (or well, should) be standard > programming practise. It is in no way special to TLS or OpenPGP. > I concur. It might as well have another paragraph as well that says: This RFC specifies the use of data. Improper use of data can cause arbitrary code execution. Care must be taken to prevent this. I think that paragraph can go. ---------- There is one other issue that I think should be cleaned up. It concerns the use of the words, "key" and "certificate." The term "PGP Key" was invented by Whit Diffie, and has a number of desirable characteristics. It's one syllable, it's an easy word to say. However, "PGP Keys" are in fact certificates that contain at least one key and at least one certification. In RFC2440 and beyond, we have used the colloquial term "key" but I think in this document the more precise term "certificate" is called for. Strictly speaking, the objects that TLS is using in this draft is a PGP Certificate with a Public Key Packet (tag 6) or Public Subkey Packet (tag 14) that is enabled for authentication implicitly or explicitly. This is why a little bit of over-precision is called for. I might present you with a single-key OpenPGP certificate that is enabled for authentication with a key flags subpacket. But I might also present you with an OpenPGP certificate that has a subkey with no key flags, which would also be reasonable. So I recommend changing "OpenPGP key" or "OpenPGP public key" to "OpenPGP certificate" throughout the document. It might be good to point out the fact that it can be a subkey. Minimally, one could change the text in 2.3: An OpenPGP public key appearing in the Certificate message will be sent using the binary OpenPGP format. The term public key is used to describe a composition of OpenPGP packets to form a block of data which contains all information needed by the peer. This includes public key packets, user ID packets and all the fields described in section 10.1 of [OpenPGP]. to An OpenPGP certificate appearing in the Certificate message will be sent using the binary OpenPGP format. The term certificate is used to describe a composition of OpenPGP packets to form a block of data which contains all information needed by the peer. This includes public key packets, subkey packets, user ID packets and all the fields described in section 10.1 of [OpenPGP]. That would work just fine and would preserve the virtue of terseness that the present draft has. Jon From renakiyama@so-net.ne.jp Wed Jun 28 06:30:11 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvXJD-00070K-DV for OPENPGP-ARCHIVE@LISTS.IETF.ORG; Wed, 28 Jun 2006 06:30:11 -0400 Received: from [218.8.141.252] (helo=allabout.co.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvXJ8-0007AD-PY for OPENPGP-ARCHIVE@LISTS.IETF.ORG; Wed, 28 Jun 2006 06:30:11 -0400 Received: from vklbzvu9 (unknown [220.193.140.213]) by smtp62 (Coremail) with SMTP id 106gOjcSQpxCwePX.1 for ; Sun, 08 Jun 2003 08:32:11 +0800 (CST) X-Originating-IP: [220.193.140.213] Subject: =?iso-2022-jp?B?GyRCJW0laiE8JT8kRyQ5GyhC?= From: =?shift-jis?B?k+yTbA==?= To: X-Mailer: Microsoft Outlook Express 6.00.2800.1478 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C3215D.80778EE0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 4.0 (++++) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C3215D.80778EE0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: base64 GyRCImMlbSVqITwlPyROJF8kRyQ5ISI2PUwjJCIka0p9JE4kX0Z+Pmw9UE1oJF4kORsoQg0KGyRC IUEhJiFBISYhQSEmIUEhJiFBISYhQSEmIUEhJiFBISYhQSEmIUEhJiFBISYhQSEmIUEhJiFBISYh QSEmIUEhJiFBISYhQSEmIUEhJhsoQg0KGyRCSWFDSiRKJCskSiQrQ2dOSSQvJEokbCRKJCQ9dztS OTtAOCRyNS5KfSRLJDQ+UjJwJDckXiQ5ISMbKEINChskQiQ0PlIycCRyPHUkMSQ/JCRKfSRPJDMk QSRpJFgbKEIgGyRCIk0hIRsoQmh0dHA6Ly92cWxoLmNvbS8/bXkxMg0KDQobJEIiKDFnPXVMNSQ3 JEchIklVJC05ZyQoJGslOyVVJWwkcjVhJGEkRiRrPXc7Ujk7QDgkTiRfJE4kND5SMnAkRyQ5ISMb KEINCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN Ci9fL18vXy9fL18vXy9fL18vXy9fL18vXy9fLw0KGyRCJWEhPCVrSVRNVxsoQg0KcF9mcmVlc3R5 bGUwNDAzQHlhaG9vLmNhIA0KDQovXy9fL18vXy9fL18vXy9fL18vXy9fL18vXy8NCg== ------=_NextPart_000_0006_01C3215D.80778EE0 Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby0yMDIyLWpwIj4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRN TCA2LjAwLjI5MDAuMjE4MCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVB RD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGlj IiANCnNpemU9Mj4bJEIiYyVtJWohPCU/JE4kXyRHJDkhIjY9TCMkIiRrSn0kTiRfRn4+bD1QTWgk XiQ5GyhCPEJSPhskQiFBISYhQSEmIUEhJiFBISYhQSEmIUEhJiFBISYhQSEmIUEhJiFBISYhQSEm IUEhJiFBISYhQSEmIUEhJiFBISYhQSEmIUEhJiFBISYbKEI8QlI+GyRCSWFDSiRKJCskSiQrQ2dO SSQvJEokbCRKJCQ9dztSOTtAOCRyNS5KfSRLJDQ+UjJwJDckXiQ5ISMbKEI8QlI+GyRCJDQ+UjJw JHI8dSQxJD8kJEp9JE8kMyRBJGkkWBsoQiANChskQiJNISEbKEI8QSBocmVmPSJodHRwOi8vdnFs aC5jb20vP215MTIiPmh0dHA6Ly92cWxoLmNvbS8/bXkxMjwvQT48L0ZPTlQ+PC9ESVY+DQo8RElW PiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIA0Kc2l6ZT0yPhsk QiIoMWc9dUw1JDckRyEiSVUkLTlnJCgkayU7JVUlbCRyNWEkYSRGJGs9dztSOTtAOCROJF8kTiQ0 PlIycCRHJDkhIxsoQjwvRk9OVD48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05U IGZhY2U9Ik1TIFVJIEdvdGhpYyIgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZP TlQgZmFjZT0iTVMgVUkgR290aGljIiBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48 Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElW PjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhpYyIgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxE SVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGljIiBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0K PERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+ DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhpYyIgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJ Vj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGljIiBzaXplPTI+PC9GT05UPiZuYnNwOzwv RElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7 PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhpYyIgc2l6ZT0yPjwvRk9OVD4mbmJz cDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGljIiBzaXplPTI+PC9GT05UPiZu YnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNpemU9Mj48L0ZPTlQ+ Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhpYyIgc2l6ZT0yPjwvRk9O VD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGljIiBzaXplPTI+PC9G T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNpemU9Mj48 L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhpYyIgc2l6ZT0y PjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGljIiBzaXpl PTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNp emU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhpYyIg c2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGlj IiBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3Ro aWMiIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdv dGhpYyIgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkg R290aGljIiBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBV SSBHb3RoaWMiIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1T IFVJIEdvdGhpYyIgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0i TVMgVUkgR290aGljIiBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNl PSJNUyBVSSBHb3RoaWMiIHNpemU9Mj4vXy9fL18vXy9fL18vXy9fL18vXy9fL18vXy88QlI+GyRC JWEhPCVrSVRNVxsoQjxCUj48QSANCmhyZWY9Im1haWx0bzpwX2ZyZWVzdHlsZTA0MDNAeWFob28u Y2EiPnBfZnJlZXN0eWxlMDQwM0B5YWhvby5jYTwvQT4gPEEgDQpocmVmPSJtYWlsdG86c19mb3Jf c3dlZXRiYWJ5QHlhaG9vLmNvLnVrIj48L0E+PEEgDQpocmVmPSJtYWlsdG86cGFfZm9yX3BhcnR5 cGFydHlAeWFob28uY28udWsiPjwvQT48QSANCmhyZWY9Im1haWx0bzpzYXNhX2luZm8wMDFAeWFo b28uY2EiPjwvQT48QlI+PEEgDQpocmVmPSJtYWlsdG86c3NfaW5mb18wMDAyQHlhaG9vLmNhIj48 L0E+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNpemU9Mj4v Xy9fL18vXy9fL18vXy9fL18vXy9fL18vXy88L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9 Ik1TIFVJIEdvdGhpYyIgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj48L0JPRFk+PC9IVE1MPg0K ------=_NextPart_000_0006_01C3215D.80778EE0-- Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5RG2EKZ027906; Tue, 27 Jun 2006 09:02:14 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k5RG2Eu6027904; Tue, 27 Jun 2006 09:02:14 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from merrymeet.com (merrymeet.com [63.73.97.162]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5RG2DKR027894 for ; Tue, 27 Jun 2006 09:02:13 -0700 (MST) (envelope-from jon@callas.org) Received: from keys.merrymeet.com (keys.merrymeet.com [63.73.97.166]) (Authenticated sender: jon) by merrymeet.com (Postfix) with ESMTP id 363861AC655 for ; Tue, 27 Jun 2006 09:02:11 -0700 (PDT) Received: from [10.13.252.251] ([212.44.18.222]) by keys.merrymeet.com (PGP Universal service); Tue, 27 Jun 2006 09:02:11 -0700 X-PGP-Universal: processed; by keys.merrymeet.com on Tue, 27 Jun 2006 09:02:11 -0700 Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <87bqsebs41.fsf@wheatstone.g10code.de> References: <87bqsebs41.fsf@wheatstone.g10code.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jon Callas Subject: Re: [Russ Housley] Fwd: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to Experimental RFC (draft-ietf-tls-openpgp-keys) Date: Tue, 27 Jun 2006 09:02:03 -0700 To: OpenPGP X-Mailer: Apple Mail (2.750) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On 27 Jun 2006, at 7:17 AM, Werner Koch wrote: > > Hi, > > I can't comment on TLS specific things but here are a few minor > things: > > 1. Introduction > > [...] > > OpenPGP keys (sometimes called OpenPGP certificates), provide > security services for electronic communications. They are widely > deployed, especially in electronic mail applications, provide > public > key authentication services, allow distributed key management > and can > be used with a non hierarchical trust model called the "web of > trust" > [WOT]. > > Because OpenPGP does not define any trust model, a wording like > > ... and allows the use in non hierarchical trust models, for > example the "Web of Trust"[WOT]. > > seems to better to me. > The important thing is that trust models are not part of OpenPGP. I think it should also say, "OpenPGP certificates (often called OpenPGP keys), ..." for reasons I'll state more fully after my comments on Werner's comments. > > [...] > > 2.3. Server Certificate > > [...] > > DHE_RSA RSA public key which can be used for > signing. > > Shouldn't this say: "RSA public key which can be used for > authentication"? Recall that OpenPGP features a key flag to indicate > an authentication key (0x20). > Yes, it should. > > [...] > > 3. Security Considerations > > As with X.509 ASN.1 formatted keys, OpenPGP keys need specialized > parsers. Care must be taken to make those parsers safe against > maliciously modified keys, that could cause arbitrary code > execution. > > That is superfluous as this is (or well, should) be standard > programming practise. It is in no way special to TLS or OpenPGP. > I concur. It might as well have another paragraph as well that says: This RFC specifies the use of data. Improper use of data can cause arbitrary code execution. Care must be taken to prevent this. I think that paragraph can go. ---------- There is one other issue that I think should be cleaned up. It concerns the use of the words, "key" and "certificate." The term "PGP Key" was invented by Whit Diffie, and has a number of desirable characteristics. It's one syllable, it's an easy word to say. However, "PGP Keys" are in fact certificates that contain at least one key and at least one certification. In RFC2440 and beyond, we have used the colloquial term "key" but I think in this document the more precise term "certificate" is called for. Strictly speaking, the objects that TLS is using in this draft is a PGP Certificate with a Public Key Packet (tag 6) or Public Subkey Packet (tag 14) that is enabled for authentication implicitly or explicitly. This is why a little bit of over-precision is called for. I might present you with a single-key OpenPGP certificate that is enabled for authentication with a key flags subpacket. But I might also present you with an OpenPGP certificate that has a subkey with no key flags, which would also be reasonable. So I recommend changing "OpenPGP key" or "OpenPGP public key" to "OpenPGP certificate" throughout the document. It might be good to point out the fact that it can be a subkey. Minimally, one could change the text in 2.3: An OpenPGP public key appearing in the Certificate message will be sent using the binary OpenPGP format. The term public key is used to describe a composition of OpenPGP packets to form a block of data which contains all information needed by the peer. This includes public key packets, user ID packets and all the fields described in section 10.1 of [OpenPGP]. to An OpenPGP certificate appearing in the Certificate message will be sent using the binary OpenPGP format. The term certificate is used to describe a composition of OpenPGP packets to form a block of data which contains all information needed by the peer. This includes public key packets, subkey packets, user ID packets and all the fields described in section 10.1 of [OpenPGP]. That would work just fine and would preserve the virtue of terseness that the present draft has. Jon Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5REMVdj000933; Tue, 27 Jun 2006 07:22:31 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k5REMVWO000932; Tue, 27 Jun 2006 07:22:31 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [217.69.77.222]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5REMTJE000914 for ; Tue, 27 Jun 2006 07:22:29 -0700 (MST) (envelope-from wk@gnupg.org) Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.50 #1 (Debian)) id 1FvEaa-0000yS-LD for ; Tue, 27 Jun 2006 16:30:52 +0200 Received: from wk by localhost with local (Exim 4.62 #1 (Debian)) id 1FvENS-0007Vg-I3 for ; Tue, 27 Jun 2006 16:17:18 +0200 From: Werner Koch To: ietf-openpgp@imc.org Subject: Re: [Russ Housley] Fwd: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to Experimental RFC (draft-ietf-tls-openpgp-keys) References: Organisation: g10 Code GmbH OpenPGP: id=5B0358A2; url=finger:wk@g10code.com Date: Tue, 27 Jun 2006 16:17:18 +0200 In-Reply-To: (Derek Atkins's message of "Tue, 27 Jun 2006 09:21:33 -0400") Message-ID: <87bqsebs41.fsf@wheatstone.g10code.de> User-Agent: Gnus/5.110006 (No Gnus v0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Hi, I can't comment on TLS specific things but here are a few minor things: 1. Introduction [...] OpenPGP keys (sometimes called OpenPGP certificates), provide security services for electronic communications. They are widely deployed, especially in electronic mail applications, provide public key authentication services, allow distributed key management and can be used with a non hierarchical trust model called the "web of trust" [WOT]. Because OpenPGP does not define any trust model, a wording like ... and allows the use in non hierarchical trust models, for example the "Web of Trust"[WOT]. seems to better to me. [...] 2.3. Server Certificate [...] DHE_RSA RSA public key which can be used for signing. Shouldn't this say: "RSA public key which can be used for authentication"? Recall that OpenPGP features a key flag to indicate an authentication key (0x20). [...] 3. Security Considerations As with X.509 ASN.1 formatted keys, OpenPGP keys need specialized parsers. Care must be taken to make those parsers safe against maliciously modified keys, that could cause arbitrary code execution. That is superfluous as this is (or well, should) be standard programming practise. It is in no way special to TLS or OpenPGP. Salam-Shalom, Werner Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5RDLg4L083804; Tue, 27 Jun 2006 06:21:42 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k5RDLg4v083803; Tue, 27 Jun 2006 06:21:42 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from mail.ihtfp.org (MAIL.IHTFP.ORG [204.107.200.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k5RDLeSV083785 for ; Tue, 27 Jun 2006 06:21:41 -0700 (MST) (envelope-from warlord@MIT.EDU) Received: from cliodev.pgp.com (CLIODEV.IHTFP.ORG [204.107.200.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cliodev.ihtfp.com", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail.ihtfp.org (Postfix) with ESMTP id 2B1F8BD844A for ; Tue, 27 Jun 2006 09:21:36 -0400 (EDT) Received: (from warlord@localhost) by cliodev.pgp.com (8.13.6/8.13.1/Submit) id k5RDLX8w008551; Tue, 27 Jun 2006 09:21:33 -0400 From: Derek Atkins To: ietf-openpgp@imc.org Subject: [Russ Housley] Fwd: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to Experimental RFC (draft-ietf-tls-openpgp-keys) Date: Tue, 27 Jun 2006 09:21:33 -0400 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --=-=-= Hey, all. I'm forwarding this on from Russ, who specifically asked for OpenPGP participants to review this document. As this is an IETF Last Call, everyone should try to take a little time to make this this document fits into the 2440/2440bis model reasonably. Comments can be sent to me, to Russ, to the TLS list, or to the IETF list depending on how you feel. Note that if you send it to me, I assume you just want it anonymized and I'll forward it on without your name attached. Happy reading! -derek --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Message-Id: <7.0.0.16.2.20060626133837.07511268@vigilsec.com> Date: Mon, 26 Jun 2006 13:40:22 -0400 To: Derek Atkins From: Russ Housley Subject: Fwd: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to Experimental RFC (draft-ietf-tls-openpgp-keys) Lines: 29 MIME-Version: 1.0 Derek: It would be good to have some OpenPGP participants review this document. Russ >To: IETF-Announce >From: The IESG >Date: Mon, 26 Jun 2006 11:50:44 -0400 >Cc: tls@ietf.org >Subject: [TLS] Last Call: 'Using OpenPGP keys for TLS authentication' to > Experimental RFC (draft-ietf-tls-openpgp-keys) > >The IESG has received a request from the Transport Layer Security WG to >consider the following document: > >- 'Using OpenPGP keys for TLS authentication ' > as an Experimental RFC > >The IESG plans to make a decision in the next few weeks, and solicits >final comments on this action. Please send any comments to the >iesg@ietf.org or ietf@ietf.org mailing lists by 2006-07-10. > >The file can be obtained via >http://www.ietf.org/internet-drafts/draft-ietf-tls-openpgp-keys-10.txt --=-=-= -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant --=-=-=-- Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k59Ca04r028170; Fri, 9 Jun 2006 05:36:00 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k59Ca0tu028169; Fri, 9 Jun 2006 05:36:00 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from mail.ihtfp.org (MAIL.IHTFP.ORG [204.107.200.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k59CZxNZ028153 for ; Fri, 9 Jun 2006 05:35:59 -0700 (MST) (envelope-from warlord@MIT.EDU) Received: from cliodev.pgp.com (CLIODEV.IHTFP.ORG [204.107.200.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cliodev.ihtfp.com", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail.ihtfp.org (Postfix) with ESMTP id B141EBD8393 for ; Fri, 9 Jun 2006 08:35:58 -0400 (EDT) Received: (from warlord@localhost) by cliodev.pgp.com (8.13.6/8.13.1/Submit) id k59CZwCl007503; Fri, 9 Jun 2006 08:35:58 -0400 From: Derek Atkins To: ietf-openpgp@imc.org Subject: (FWD) Internet-Drafts Submission Cutoff Dates for the 66th IETF Meeting in Montreal, Quebec, Canada Date: Fri, 09 Jun 2006 08:35:57 -0400 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --=-=-= In case any of you are polishing up drafts for discussion in Montreal, the cutoff dates are coming quickly. Just a reminder from your friendly neighborhood working-group chair. -derek --=-=-= Content-Type: message/rfc822 Content-Disposition: inline To: ietf-announce@ietf.org From: ietf-secretariat@ietf.org Date: Fri, 09 Jun 2006 00:00:01 -0400 Subject: Internet-Drafts Submission Cutoff Dates for the 66th IETF Meeting in Montreal, Quebec, Canada Lines: 41 MIME-Version: 1.0 There are two (2) Internet-Draft cutoff dates for the 66th IETF Meeting in Montreal, Quebec, Canada: June 19th: Cutoff Date for Initial (i.e., version -00) Internet-Draft Submissions All initial Internet-Drafts (version -00) must be submitted by Monday, June 19th at 9:00 AM ET. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they can be processed or announced. The Secretariat would appreciate receiving WG Chair approval by Monday, June 12th at 9:00 AM ET. June 26th: Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft Submissions All revised Internet-Drafts (version -01 and higher) must be submitted by Monday, June 26th at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective cutoff dates will not be made available in the Internet-Drafts directory or announced until on or after Monday, July 10th at 9:00 AM ET, when Internet-Draft posting resumes. Please do not wait until the last minute to submit. Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 66th IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_dates_66.html. --=-=-= -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant --=-=-=-- Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57GjRhR099611; Wed, 7 Jun 2006 09:45:28 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k57GjRKt099610; Wed, 7 Jun 2006 09:45:27 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from mail.links.org (mail.links.org [217.155.92.109]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57GjQ0E099583 for ; Wed, 7 Jun 2006 09:45:27 -0700 (MST) (envelope-from ben@algroup.co.uk) Received: from [193.133.15.218] (localhost [127.0.0.1]) by mail.links.org (Postfix) with ESMTP id 321DD33C1C; Wed, 7 Jun 2006 17:45:25 +0100 (BST) Message-ID: <44870264.5010402@algroup.co.uk> Date: Wed, 07 Jun 2006 17:44:20 +0100 From: Ben Laurie User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: vedaal@hush.com CC: ietf-openpgp@imc.org Subject: Re: Topic/Speaker requests for Montreal References: <20060607151011.420BDDA82A@mailserver8.hushmail.com> In-Reply-To: <20060607151011.420BDDA82A@mailserver8.hushmail.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: vedaal@hush.com wrote: > > > On Wed, 07 Jun 2006 08:44:17 -0400 Derek Atkins > wrote: > >> Now is the time to revive those drafts that we sidelined to get >> 2440bis out the door. Topics that have been brought to my >> attention >> (and that I recall at the moment): >> >> PFS >> Alternate Ciphers >> OpenPGP Mail Header >> IPsec > > would like to suggest/request the topic of 'Deniable > Authentication' > > specifically, the Ian Brown - Adam Back proposed solution > of a signature on the session key hashed with recipient's public > key > > http://www.cs.ucl.ac.uk/staff/I.Brown/nts.htm Grrr, it uses the "non-repudiation" word. But, sounds like a good idea to me. -- http://www.apache-ssl.org/ben.html http://www.links.org/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57FADDS066374; Wed, 7 Jun 2006 08:10:13 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k57FADWN066373; Wed, 7 Jun 2006 08:10:13 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.135]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57FACCA066367 for ; Wed, 7 Jun 2006 08:10:12 -0700 (MST) (envelope-from vedaal@hush.com) Received: from smtp3.hushmail.com (localhost.hushmail.com [127.0.0.1]) by smtp3.hushmail.com (Postfix) with SMTP id DEBC4A3491 for ; Wed, 7 Jun 2006 08:10:11 -0700 (PDT) Received: from mailserver8.hushmail.com (mailserver8.hushmail.com [65.39.178.61]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Wed, 7 Jun 2006 08:10:11 -0700 (PDT) Received: by mailserver8.hushmail.com (Postfix, from userid 65534) id 420BDDA82A; Wed, 7 Jun 2006 08:10:11 -0700 (PDT) Date: Wed, 07 Jun 2006 11:10:10 -0400 To: Cc: Subject: Re: Topic/Speaker requests for Montreal From: Content-type: text/plain; charset="UTF-8" Message-Id: <20060607151011.420BDDA82A@mailserver8.hushmail.com> Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Wed, 07 Jun 2006 08:44:17 -0400 Derek Atkins wrote: >Now is the time to revive those drafts that we sidelined to get >2440bis out the door. Topics that have been brought to my >attention >(and that I recall at the moment): > > PFS > Alternate Ciphers > OpenPGP Mail Header > IPsec would like to suggest/request the topic of 'Deniable Authentication' specifically, the Ian Brown - Adam Back proposed solution of a signature on the session key hashed with recipient's public key http://www.cs.ucl.ac.uk/staff/I.Brown/nts.htm as it would involve the addition of a new packet type, rather than changing any existing packets, it might not be as difficult to incorporate into open-pgp Thanks, vedaal Concerned about your privacy? Instantly send FREE secure email, no account required http://www.hushmail.com/send?l=480 Get the best prices on SSL certificates from Hushmail https://www.hushssl.com?l=485 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57CiQxE023902; Wed, 7 Jun 2006 05:44:26 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k57CiQ4j023900; Wed, 7 Jun 2006 05:44:26 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from mail.ihtfp.org (MAIL.IHTFP.ORG [204.107.200.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k57CiPJF023883 for ; Wed, 7 Jun 2006 05:44:26 -0700 (MST) (envelope-from warlord@MIT.EDU) Received: from cliodev.pgp.com (CLIODEV.IHTFP.ORG [204.107.200.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cliodev.ihtfp.com", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail.ihtfp.org (Postfix) with ESMTP id 2A7FEBD8393 for ; Wed, 7 Jun 2006 08:44:23 -0400 (EDT) Received: (from warlord@localhost) by cliodev.pgp.com (8.13.6/8.13.1/Submit) id k57CiHQl004324; Wed, 7 Jun 2006 08:44:17 -0400 From: Derek Atkins To: ietf-openpgp@imc.org Subject: Topic/Speaker requests for Montreal Date: Wed, 07 Jun 2006 08:44:17 -0400 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Hi, Montreal is just around the corner. What with 2440bis "done", it's time to get down to other projects. I've requested a 1-hour timeslot in Montreal so we can discuss other OpenPGP related topics. Now is the time to revive those drafts that we sidelined to get 2440bis out the door. Topics that have been brought to my attention (and that I recall at the moment): PFS Alternate Ciphers OpenPGP Mail Header IPsec If you've got a draft and want to present it, let me know how much time you want. If you'd got an idea that you'd like to present but no draft, let me know that, too. Thanks! -derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56Ke5Zb049635; Tue, 6 Jun 2006 13:40:05 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k56Ke5G5049634; Tue, 6 Jun 2006 13:40:05 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from foobar.cs.jhu.edu (foobar.cs.jhu.edu [128.220.13.173]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56Ke4du049626 for ; Tue, 6 Jun 2006 13:40:04 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.hsd1.ma.comcast.net (walrus.hsd1.ma.comcast.net [24.60.132.70]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id k56Ke3k07167 for ; Tue, 6 Jun 2006 16:40:03 -0400 Received: from grover.jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.hsd1.ma.comcast.net (8.13.6/8.13.6) with ESMTP id k56KifX0022431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 6 Jun 2006 16:44:41 -0400 Received: from grover.jabberwocky.com (grover.jabberwocky.com [127.0.0.1]) by grover.jabberwocky.com (8.13.1/8.13.1) with ESMTP id k56Kdvjh011479 for ; Tue, 6 Jun 2006 16:39:57 -0400 Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id k56Kdtt1011478 for ietf-openpgp@imc.org; Tue, 6 Jun 2006 16:39:55 -0400 Date: Tue, 6 Jun 2006 16:39:55 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: Re: DSA2 test material Message-ID: <20060606203955.GB11349@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org References: <20060606193954.96E0BDA827@mailserver7.hushmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060606193954.96E0BDA827@mailserver7.hushmail.com> OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.11 Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Tue, Jun 06, 2006 at 03:39:54PM -0400, vedaal@hush.com wrote: > > On Tue, 06 Jun 2006 12:09:39 -0400 David Shaw > wrote: > > >I have put together some sample keys and signatures to help test > >DSA2 > >interoperability and posted the lot at > >http://www.jabberwocky.com/openpgp/dsa2.tar.gz > > > >Note that the current released version of GnuPG (1.4.3) can > >verify, > >but will not generate a DSA2 signature or key. > > > tested them in gnupg (1.4.3 mingw32 on win2k pro) > > got a few error messages: > all involving the '224' type > > was this meant to be tested in 1.4.3 ? No. This is meant for people developing OpenPGP implementations other than GPG. David Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56JdxWM033628; Tue, 6 Jun 2006 12:39:59 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k56JdxAh033627; Tue, 6 Jun 2006 12:39:59 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.135]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56Jdwha033620 for ; Tue, 6 Jun 2006 12:39:58 -0700 (MST) (envelope-from vedaal@hush.com) Received: from smtp3.hushmail.com (localhost.hushmail.com [127.0.0.1]) by smtp3.hushmail.com (Postfix) with SMTP id ED9C9A3508 for ; Tue, 6 Jun 2006 12:39:56 -0700 (PDT) Received: from mailserver7.hushmail.com (mailserver7.hushmail.com [65.39.178.62]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Tue, 6 Jun 2006 12:39:54 -0700 (PDT) Received: by mailserver7.hushmail.com (Postfix, from userid 65534) id 96E0BDA827; Tue, 6 Jun 2006 12:39:54 -0700 (PDT) Date: Tue, 06 Jun 2006 15:39:54 -0400 To: Cc: Subject: Re: DSA2 test material From: Content-type: text/plain; charset="UTF-8" Message-Id: <20060606193954.96E0BDA827@mailserver7.hushmail.com> Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Tue, 06 Jun 2006 12:09:39 -0400 David Shaw wrote: >I have put together some sample keys and signatures to help test >DSA2 >interoperability and posted the lot at >http://www.jabberwocky.com/openpgp/dsa2.tar.gz > >Note that the current released version of GnuPG (1.4.3) can >verify, >but will not generate a DSA2 signature or key. tested them in gnupg (1.4.3 mingw32 on win2k pro) got a few error messages: all involving the '224' type was this meant to be tested in 1.4.3 ? here is the ouptut summary of gpg --version gpg (GnuPG) 1.4.3 Copyright (C) 2006 Free Software Foundation, Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the file COPYING for details. Home: V:/ Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA Cipher: IDEA (S1), 3DES (S2), CAST5 (S3), BLOWFISH (S4), AES (S7), AES192 (S8), AES256 (S9), TWOFISH (S10) Hash: MD5 (H1), SHA1 (H2), RIPEMD160 (H3), SHA256 (H8), SHA384 (H9), SHA512 (H10) Compression: Uncompressed (Z0), ZIP (Z1), ZLIB (Z2), BZIP2 (Z3) a hash of 224 is not listed so, not unexpectely, upon importing the key, since gnupg didn't recognize the 224 hash, it also didn't recognize the self-sig here are the gnupg error messages (using verbose verbose setting): [1] gpg: pub 2048D/41FBF40E 2006-05-26 gpg: key 41FBF40E: invalid self-signature on user ID "DSA-2048-224" gpg: key 41FBF40E: skipped user ID "DSA-2048-224" gpg: key 41FBF40E: no valid user IDs gpg: this may be caused by a missing self-signature gpg: Total number processed: 1 gpg: w/o user IDs: 1 File: V:\dsa2tf\DSA2-Tests\keys\DSA-2048-224.pub Time: 6/6/2006 2:37:52 PM (6/6/2006 6:37:52 PM UTC) [2] gpg: original file name='dsa-1024-224-sign' gpg: md_enable: algorithm 11 not available gpg: Signature made 5/27/2006 23:03:25 using DSA key ID 94D38E40 gpg: Can't check signature: unknown digest algorithm File: V:\dsa2tf\DSA2-Tests\sigs\dsa-1024-224-sign.gpg Time: 6/6/2006 2:47:01 PM (6/6/2006 6:47:01 PM UTC) [3] gpg: original file name='dsa-2048-224-sign' gpg: md_enable: algorithm 11 not available gpg: Signature made 5/27/2006 19:33:49 using DSA key ID 41FBF40E gpg: Can't check signature: unknown digest algorithm File: V:\dsa2tf\DSA2-Tests\sigs\dsa-2048-224-sign.gpg Time: 6/6/2006 3:04:25 PM (6/6/2006 7:04:25 PM UTC) vedaal Concerned about your privacy? Instantly send FREE secure email, no account required http://www.hushmail.com/send?l=480 Get the best prices on SSL certificates from Hushmail https://www.hushssl.com?l=485 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56G9tbl067462; Tue, 6 Jun 2006 09:09:55 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k56G9tCt067461; Tue, 6 Jun 2006 09:09:55 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f Received: from foobar.cs.jhu.edu (foobar.cs.jhu.edu [128.220.13.173]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k56G9qGW067394 for ; Tue, 6 Jun 2006 09:09:55 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.hsd1.ma.comcast.net (walrus.hsd1.ma.comcast.net [24.60.132.70]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id k56G9jk05434 for ; Tue, 6 Jun 2006 12:09:45 -0400 Received: from grover.jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.hsd1.ma.comcast.net (8.13.6/8.13.6) with ESMTP id k56GEMBS020459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 6 Jun 2006 12:14:22 -0400 Received: from grover.jabberwocky.com (grover.jabberwocky.com [127.0.0.1]) by grover.jabberwocky.com (8.13.1/8.13.1) with ESMTP id k56G9ddC010875 for ; Tue, 6 Jun 2006 12:09:39 -0400 Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id k56G9d6p010874 for ietf-openpgp@imc.org; Tue, 6 Jun 2006 12:09:39 -0400 Date: Tue, 6 Jun 2006 12:09:39 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: DSA2 test material Message-ID: <20060606160939.GC28850@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.11 Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: I have put together some sample keys and signatures to help test DSA2 interoperability and posted the lot at http://www.jabberwocky.com/openpgp/dsa2.tar.gz Note that the current released version of GnuPG (1.4.3) can verify, but will not generate a DSA2 signature or key. The next version will allow generation of DSA2 keys if the --enable-dsa2 option is given (off by default to try and minimize the "Hey, neat, a bigger key. What do you mean most of the world can't verify my signatures?" factor). The readme file: This archive contains material to help verify interoperability to the OpenPGP DSA2 design as implemented in GnuPG. Keys are located in the keys directory. Included are: 1024 bits, 160 bit q size (i.e. regular old DSA) 2048 bits, 224 bit q size 3072 bits, 256 bit q size 7680 bits, 384 bit q size 15360 bits, 512 bit q size All secret keys have the passphrase "test". Note the inclusion of 7680/384 and 15360/512 keys. They're large, inconvenient and absurdly slow. GnuPG will accept any size key, but will not generate DSA keys over 3072 bits. I include these keys mainly for be-liberal-in-what-you-accept testing. There are are signatures issued by these keys in the sigs directory. The filenames indicate the key used to make the signature, and the number of bits of the hash. In the case of the 1024-bit DSA key (160-bit q size), there are 5 signatures using different hashes. This is to demonstrate hash truncation to fit in the 160-bit hash size of that key. File Key size Hash ---------------------- ---------- ------- dsa-1024-160-sign.gpg 1024 bits SHA-1 dsa-1024-224-sign.gpg 1024 bits SHA-224 (truncated to 160 bits) dsa-1024-256-sign.gpg 1024 bits SHA-256 (truncated to 160 bits) dsa-1024-384-sign.gpg 1024 bits SHA-384 (truncated to 160 bits) dsa-1024-512-sign.gpg 1024 bits SHA-512 (truncated to 160 bits) dsa-2048-224-sign.gpg 2048 bits SHA-224 dsa-3072-256-sign.gpg 3072 bits SHA-256 dsa-7680-384-sign.gpg 7680 bits SHA-384 dsa-15360-512-sign.gpg 15360 bits SHA-512 David