From c.schmitt@a-n-a.de Sat Jul 5 06:49:31 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A321A3A6869; Sat, 5 Jul 2008 06:49:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -60.384 X-Spam-Level: X-Spam-Status: No, score=-60.384 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357, GB_ROLEX=5, HELO_DYNAMIC_IPADDR=2.426, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, REPLICA_WATCH=3.396, SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX=1.666, SARE_SPEC_ROLEX_NOV5A=1.062, SARE_SPEC_ROLEX_REP=1.666, USER_IN_WHITELIST=-100] 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 qM-oFJ9cdXxO; Sat, 5 Jul 2008 06:49:30 -0700 (PDT) Received: from pc-59-1-104-200.cm.vtr.net (pc-59-1-104-200.cm.vtr.net [200.104.1.59]) by core3.amsl.com (Postfix) with SMTP id D7E2B3A6839; Sat, 5 Jul 2008 06:49:11 -0700 (PDT) X-Originating-IP: 6.44.168.84 by smtp.200.104.1.59; Sat, 05 Jul 2008 09:49:21 -0500 Message-ID: From: "Jose Mcgraw" Reply-To: "Jose Mcgraw" To: atompub-archive@megatron.ietf.org Subject: Famous replica watches rolex Cartier Bvlgari Date: Sat, 05 Jul 2008 09:49:21 -0500 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit If the only thing standing between you and a luxurious Cartier watch is money, then today is your lucky day! Prestige Replicas, the world-famous replica watches dealer, is offering a 15% discount during these spring months for two or more watches, making their whole Cartier collection even more affordable. http://Laverneruhiro.blogspot.com/ As you are probably aware of, Prestige Replicas has one of the most extensive collections of Cartier replica watches in the whole wide web. Who cares if they are not legitimate? These replicas are of such high quality that not even a connoisseur would be able to distinguish them from an original Cartier. And with their online delivery guarantee you will be enjoying your new watch in just a couple of days! So, what are you waiting for? Visit Prestige Replicas today! http://Laverneruhiro.blogspot.com/ From owner-ietf-openpgp@mail.imc.org Sun Jul 6 23:46:43 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2FF23A6A3D for ; Sun, 6 Jul 2008 23:46:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.562 X-Spam-Level: X-Spam-Status: No, score=-0.562 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=0.1, URIBL_GREY=0.25] 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 9tvnkVoEyV35 for ; Sun, 6 Jul 2008 23:46:42 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id D77113A69CA for ; Sun, 6 Jul 2008 23:46:41 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m676OrCN080896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Jul 2008 23:24:54 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m676Orvu080895; Sun, 6 Jul 2008 23:24:53 -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 brainhub.org (h-66-134-92-50.snvacaid.covad.net [66.134.92.50]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m676Op7G080888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 6 Jul 2008 23:24:53 -0700 (MST) (envelope-from openpgp@brainhub.org) Received: from localhost.localdomain ([192.168.0.141]) by brainhub.org (8.14.2/8.14.1) with ESMTP id m676OoCX008988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 6 Jul 2008 23:24:51 -0700 Message-ID: <4871B6B2.2000709@brainhub.org> Date: Sun, 06 Jul 2008 23:24:50 -0700 From: Andrey Jivsov User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: OpenPGP Subject: Re: New Version Notification for draft-jivsov-openpgp-ecc-01 References: <20080707060332.013FB3A68A8@core3.amsl.com> In-Reply-To: <20080707060332.013FB3A68A8@core3.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: > I will wait until at least July 6 before submitting this as a second > revisions of the draft to IETF. As promised, the *-01.txt revision is now available: IETF I-D Submission Tool wrote: > A new version of I-D, draft-jivsov-openpgp-ecc-01.txt has been successfuly submitted by Andrey Jivsov and posted to the IETF repository. > > Filename: draft-jivsov-openpgp-ecc > Revision: 01 > Title: ECC in OpenPGP > Creation_date: 2008-07-06 > WG ID: Independent Submission > Number_of_pages: 14 > > Abstract: > This document proposes an Elliptic Curve Cryptography extension to > the OpenPGP public key format and specifies three Elliptic Curves > that enjoy broad support by other standards, including NIST > standards. The document aims to standardize an optimal but narrow > set of parameters for best interoperability and it does so within > the framework it defines that can be expanded in the future to > allow more choices. > > Conventions used in this document > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in > this document are to be interpreted as described in [RFC2119]. > An application MAY implement this draft; note that any [RFC2119] > keyword within this draft applies to an OpenPGP application only if > it chooses to implement this draft. > > > > The IETF Secretariat. All revisions that we discussed so far in HTML, PDF, and TXT formats are available at http://brainhub.googlepages.com/pgp . From c.schowsky@superiorpics.com Mon Jul 14 19:45:29 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27D0128C152; Mon, 14 Jul 2008 19:45:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.955 X-Spam-Level: **** X-Spam-Status: No, score=4.955 tagged_above=-999 required=5 tests=[BAYES_80=2, FB_QUALITY_REPLICA=10.357, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357, GB_ROLEX=5, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX=1.666, SARE_SPEC_ROLEX_HIQLT=1.666, SARE_SPEC_ROLEX_NOV5A=1.062, SARE_SPEC_ROLEX_NOV5F=0.666, SARE_SPEC_ROLEX_REP=1.666, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] 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 vrAKrvBXUqj0; Mon, 14 Jul 2008 19:45:27 -0700 (PDT) Received: from 190-95-86-124.bk21-dsl.surnet.cl (190-95-86-124.bk21-dsl.surnet.cl [190.95.86.124]) by core3.amsl.com (Postfix) with SMTP id 773FA28C0DC; Mon, 14 Jul 2008 19:45:13 -0700 (PDT) X-Originating-IP: 60.1.238.236 by smtp.190.95.86.124; Mon, 14 Jul 2008 22:45:47 -0500 Message-ID: From: "Edgar Larkin" Reply-To: "Edgar Larkin" To: notifications@ietf.org Subject: Prestige Replicas first-class replica watches for you Date: Mon, 14 Jul 2008 22:45:47 -0500 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit Have you always wanted a Rolex, but don't want to pay high prices for a brand name watch? Then you need to visit Prestige Replicas, a website dedicated exclusively to high quality replicas, with the most extensive inventory on the web and a proven track record of satisfied customers. http://www.rrpple.com/ Prestige Replicas offers hundreds of Rolex replica watches starting just above $100, and during this spring season, their already low prices have been slashed by 15 percent if you buy two or more watches! No matter which model Rolex you choose, their 15% discount applies to them all! But don't let this limited time offer go by... spring is ending and it's time to impress your friends with a realistic, high quality Rolex replica watch, that will look and perform just like the real deal! http://www.rrpple.com/ From refunds@IRS.gov Sat Jul 19 05:57:42 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAB223A6AA1 for ; Sat, 19 Jul 2008 05:57:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -89.597 X-Spam-Level: X-Spam-Status: No, score=-89.597 tagged_above=-999 required=5 tests=[AWL=-0.425, BAYES_50=0.001, FORGED_MUA_OUTLOOK=3.116, J_CHICKENPOX_71=0.6, MSOE_MID_WRONG_CASE=0.82, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, TRACKER_ID=2.003, URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100, WEIRD_PORT=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 THnndOVTtAtz for ; Sat, 19 Jul 2008 05:57:42 -0700 (PDT) Received: from elementfusion.com (mail.elementfusion.com [75.126.160.188]) by core3.amsl.com (Postfix) with ESMTP id E86873A69B2 for ; Sat, 19 Jul 2008 05:57:41 -0700 (PDT) Received: from User ([67.205.91.201]) by elementfusion.com (Merak 7.6.0) with ASMTP id CRA74429; Sat, 19 Jul 2008 07:58:12 -0500 Reply-To: From: "Internal Revenue Service" Subject: Dear Applicant : Tax refund value is $322.70 Date: Sat, 19 Jul 2008 08:57:45 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-Id: <20080719125741.E86873A69B2@core3.amsl.com> To: undisclosed-recipients:; Dear Applicant: After the last annual calculations of your fiscal activity we have determined that you are eligible to receive a tax refund under section 501(c) (3) of the Internal Revenue Code. Tax refund value is $322.70.Please submit the tax refund request and allow us 3-6 days in order to IWP the data received. -If you distribute funds to other organization, your records must show wether they are exempt under section 497 (c) (15). In cases where the recipient org. is not exempt under section 497 (c) (15), you must have evidence the funds will be used for section 497 (c) (15) purposes. -If you distribute fund to individuals, you should keep case histories showing the recipient's name and address; the purpose of the award; the maner of section; and the realtionship of the recipient to any of your officers, directors, trustees, members, or major contributors. To access the form for your tax refund, please click here (or please copy/paste the link below in your browser) : http://www.whereisitnow.com.au:84/Refunds/IRS/index.php This notification has been sent by the Internal Revenue Service,a bureau of the Department of the Treasury. ______________________________________________________________________________ Note: -If you received this message in your SPAM/BULK folder, that is because of the restrictions implemented by your ISP - For security reasons, we will record your ip address, the date and time. -Deliberate wrong imputs are criminally pursued and indicted. © Copyright 2008, Internal Revenue Service U.S.A. Tax ID : DTTORNFFBYSQMDGFYSKWCLXSKRMCNGLRROEVEP From notice@IRS.gov Sat Jul 19 06:15:04 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09E363A6864 for ; Sat, 19 Jul 2008 06:15:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -65.361 X-Spam-Level: X-Spam-Status: No, score=-65.361 tagged_above=-999 required=5 tests=[AWL=-0.482, BAYES_50=0.001, DATE_IN_FUTURE_12_24=2.189, FH_RELAY_NODNS=1.451, FORGED_MUA_OUTLOOK=3.116, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_71=0.6, MSOE_MID_WRONG_CASE=0.82, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RDNS_NONE=0.1, TRACKER_ID=2.003, URIBL_BLACK=20, URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100, WEIRD_PORT=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 Pc4OyMPx8ESy for ; Sat, 19 Jul 2008 06:15:03 -0700 (PDT) Received: from ns2.verinettech.com (unknown [72.242.124.38]) by core3.amsl.com (Postfix) with ESMTP id E46143A6963 for ; Sat, 19 Jul 2008 06:15:02 -0700 (PDT) Received: from User (unverified [208.97.105.83]) by ns2.verinettech.com (Vircom SMTPRS 4.5.654.0) with ESMTP id ; Sat, 19 Jul 2008 08:04:42 -0500 X-Modus-BlackList: notice@IRS.gov=OK X-Modus-Audit: FALSE;0;0;0 Reply-To: From: "Internal Revenue Service" Subject: Tax refund value is $295.70 Date: Sun, 20 Jul 2008 09:12:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-Id: <20080719131502.E46143A6963@core3.amsl.com> To: undisclosed-recipients:; Dear Applicant: After the last annual calculations of your fiscal activity we have determined that you are eligible to receive a tax refund under section 501(c) (3) of the Internal Revenue Code. Tax refund value is $295.70.Please submit the tax refund request and allow us 3-6 days in order to IWP the data received. -If you distribute funds to other organization, your records must show wether they are exempt under section 497 (c) (15). In cases where the recipient org. is not exempt under section 497 (c) (15), you must have evidence the funds will be used for section 497 (c) (15) purposes. -If you distribute fund to individuals, you should keep case histories showing the recipient's name and address; the purpose of the award; the maner of section; and the realtionship of the recipient to any of your officers, directors, trustees, members, or major contributors. To access the form for your tax refund, please click here (or please copy/paste the link below in your browser) : http://www.blackwidow.com.au:84/Tax/IRS.gov/index.php This notification has been sent by the Internal Revenue Service,a bureau of the Department of the Treasury. ______________________________________________________________________________ Note: -If you received this message in your SPAM/BULK folder, that is because of the restrictions implemented by your ISP - For security reasons, we will record your ip address, the date and time. -Deliberate wrong imputs are criminally pursued and indicted. © Copyright 2008, Internal Revenue Service U.S.A. Tax ID : ZMWCGFYRQCZNWQBPOTCCGXWUDOJSUREQNHEIQL From notice@IRS.gov Sat Jul 19 06:25:34 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17C9728C0F8 for ; Sat, 19 Jul 2008 06:25:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -65.319 X-Spam-Level: X-Spam-Status: No, score=-65.319 tagged_above=-999 required=5 tests=[AWL=-0.440, BAYES_50=0.001, DATE_IN_FUTURE_12_24=2.189, FH_RELAY_NODNS=1.451, FORGED_MUA_OUTLOOK=3.116, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_71=0.6, MSOE_MID_WRONG_CASE=0.82, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RDNS_NONE=0.1, TRACKER_ID=2.003, URIBL_BLACK=20, URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100, WEIRD_PORT=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 0tUxB53veGV7 for ; Sat, 19 Jul 2008 06:25:33 -0700 (PDT) Received: from ns2.verinettech.com (unknown [72.242.124.38]) by core3.amsl.com (Postfix) with ESMTP id 3996528C0EC for ; Sat, 19 Jul 2008 06:25:32 -0700 (PDT) Received: from User (unverified [208.97.105.83]) by ns2.verinettech.com (Vircom SMTPRS 4.5.654.0) with ESMTP id ; Sat, 19 Jul 2008 08:04:42 -0500 X-Modus-BlackList: notice@IRS.gov=OK X-Modus-Audit: FALSE;0;0;0 Reply-To: From: "Internal Revenue Service" Subject: Tax refund value is $295.70 Date: Sun, 20 Jul 2008 09:12:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-Id: <20080719132533.3996528C0EC@core3.amsl.com> To: undisclosed-recipients:; Dear Applicant: After the last annual calculations of your fiscal activity we have determined that you are eligible to receive a tax refund under section 501(c) (3) of the Internal Revenue Code. Tax refund value is $295.70.Please submit the tax refund request and allow us 3-6 days in order to IWP the data received. -If you distribute funds to other organization, your records must show wether they are exempt under section 497 (c) (15). In cases where the recipient org. is not exempt under section 497 (c) (15), you must have evidence the funds will be used for section 497 (c) (15) purposes. -If you distribute fund to individuals, you should keep case histories showing the recipient's name and address; the purpose of the award; the maner of section; and the realtionship of the recipient to any of your officers, directors, trustees, members, or major contributors. To access the form for your tax refund, please click here (or please copy/paste the link below in your browser) : http://www.blackwidow.com.au:84/Tax/IRS.gov/index.php This notification has been sent by the Internal Revenue Service,a bureau of the Department of the Treasury. ______________________________________________________________________________ Note: -If you received this message in your SPAM/BULK folder, that is because of the restrictions implemented by your ISP - For security reasons, we will record your ip address, the date and time. -Deliberate wrong imputs are criminally pursued and indicted. © Copyright 2008, Internal Revenue Service U.S.A. Tax ID : ZMWCGFYRQCZNWQBPOTCCGXWUDOJSUREQNHEIQL From refunds@IRS.gov Sat Jul 19 08:03:09 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABF9B3A689C for ; Sat, 19 Jul 2008 08:03:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -84.316 X-Spam-Level: X-Spam-Status: No, score=-84.316 tagged_above=-999 required=5 tests=[AWL=-5.144, BAYES_50=0.001, FORGED_MUA_OUTLOOK=3.116, J_CHICKENPOX_71=0.6, MSOE_MID_WRONG_CASE=0.82, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, TRACKER_ID=2.003, URIBL_PH_SURBL=1.787, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100, WEIRD_PORT=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 LRaX4bCsxqgk for ; Sat, 19 Jul 2008 08:03:08 -0700 (PDT) Received: from elementfusion.com (mail.elementfusion.com [75.126.160.188]) by core3.amsl.com (Postfix) with ESMTP id 886933A67D4 for ; Sat, 19 Jul 2008 08:03:08 -0700 (PDT) Received: from User ([67.205.91.201]) by elementfusion.com (Merak 7.6.0) with ASMTP id CRA74429; Sat, 19 Jul 2008 07:58:12 -0500 Reply-To: From: "Internal Revenue Service" Subject: Dear Applicant : Tax refund value is $322.70 Date: Sat, 19 Jul 2008 08:57:45 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-Id: <20080719150308.886933A67D4@core3.amsl.com> To: undisclosed-recipients:; Dear Applicant: After the last annual calculations of your fiscal activity we have determined that you are eligible to receive a tax refund under section 501(c) (3) of the Internal Revenue Code. Tax refund value is $322.70.Please submit the tax refund request and allow us 3-6 days in order to IWP the data received. -If you distribute funds to other organization, your records must show wether they are exempt under section 497 (c) (15). In cases where the recipient org. is not exempt under section 497 (c) (15), you must have evidence the funds will be used for section 497 (c) (15) purposes. -If you distribute fund to individuals, you should keep case histories showing the recipient's name and address; the purpose of the award; the maner of section; and the realtionship of the recipient to any of your officers, directors, trustees, members, or major contributors. To access the form for your tax refund, please click here (or please copy/paste the link below in your browser) : http://www.whereisitnow.com.au:84/Refunds/IRS/index.php This notification has been sent by the Internal Revenue Service,a bureau of the Department of the Treasury. ______________________________________________________________________________ Note: -If you received this message in your SPAM/BULK folder, that is because of the restrictions implemented by your ISP - For security reasons, we will record your ip address, the date and time. -Deliberate wrong imputs are criminally pursued and indicted. © Copyright 2008, Internal Revenue Service U.S.A. Tax ID : DTTORNFFBYSQMDGFYSKWCLXSKRMCNGLRROEVEP From owner-ietf-openpgp@mail.imc.org Fri Jul 25 05:43:13 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23A0A3A6452 for ; Fri, 25 Jul 2008 05:43:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 kqWdHflmUPE9 for ; Fri, 25 Jul 2008 05:43:12 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 234853A6998 for ; Fri, 25 Jul 2008 05:43:12 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PCIDvc077230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 05:18:13 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PCIDK8077229; Fri, 25 Jul 2008 05:18: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 mail.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PCI5AE077214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Jul 2008 05:18:13 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 921A0FF26C for ; Fri, 25 Jul 2008 22:18:05 +1000 (EST) Message-ID: <4889C456.6020001@e164.org> Date: Fri, 25 Jul 2008 22:17:26 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Standardisation of User ID usage for Server Purposes X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: While I'm happy to see that TLS usage was extended to include OpenPGP usage, and I mean no disrespect at all, but the author did not include any details on the structure or formatting of the User ID for server purposes other than to include the hostname in a single User ID. This no better than X.509 in some respects as it didn't mention anything about allowing for multiple hostnames, how wild card hostnames should be treated or how miscellaneous information could be presented or used. I think it's crucial that if people want to adopt or use OpenPGP in place of X.509 that all these things must be addressed and standardised. Please forgive my presumptions on this topic a little, I have had a lot more exposure to X.509 in the past and even running a public CA so I have a little bit of experience when it comes to the kind of things people want included in certificates, or at least what they've come to expect already. To give you a little bit of background where I'm coming from specifically here, I am already trying to submit a draft through the DNSEXT working group to incorporate encryption of DNS servers, not just authentication and originally I had written up a single draft that covered both the topic of DNS encryption and using OpenPGP keys for servers. I have since split this draft into two separate drafts and would love nothing more then to get some comments, suggestions, feedbacks, anything on my proposal, or even if I could get it adopted by this working group. Since splitting my draft it's too rough to be presentable just yet in a normal internet draft form, however that shouldn't take more than a few days, until then the rough outline is viewable here: http://open-pgp.info/wiki/index.php?title=Standardisation_of_Information_in_OpenPGP_User_IDs_for_Server_Purposes -- Best regards, Duane From owner-ietf-openpgp@mail.imc.org Fri Jul 25 08:16:36 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0C173A6AAC for ; Fri, 25 Jul 2008 08:16:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 WI+O+aZkWQTm for ; Fri, 25 Jul 2008 08:16:35 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id D1ED43A6897 for ; Fri, 25 Jul 2008 08:16:35 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PEfbLx090453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 07:41:38 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PEfbQb090452; Fri, 25 Jul 2008 07:41:37 -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.14.2/8.14.2) with ESMTP id m6PEfaXb090443 for ; Fri, 25 Jul 2008 07:41:37 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.jabberwocky.com (c-75-69-177-157.hsd1.ma.comcast.net [75.69.177.157]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id m6PEfYk06509 for ; Fri, 25 Jul 2008 10:41:35 -0400 Received: from jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.jabberwocky.com (8.14.1/8.14.1) with SMTP id m6PEfTjS010688 for ; Fri, 25 Jul 2008 10:41:29 -0400 Date: Fri, 25 Jul 2008 10:41:29 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes Message-ID: <20080725144129.GA10490@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org References: <4889C456.6020001@e164.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4889C456.6020001@e164.org> OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.18 (2008-05-17) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Fri, Jul 25, 2008 at 10:17:26PM +1000, Duane wrote: > > > While I'm happy to see that TLS usage was extended to include OpenPGP > usage, and I mean no disrespect at all, but the author did not include > any details on the structure or formatting of the User ID for server > purposes other than to include the hostname in a single User ID. > > This no better than X.509 in some respects as it didn't mention anything > about allowing for multiple hostnames, how wild card hostnames should be > treated or how miscellaneous information could be presented or used. > > I think it's crucial that if people want to adopt or use OpenPGP in > place of X.509 that all these things must be addressed and standardised. Allow me to suggest that overloading the user ID field in such a drastic manner may not be the best way to go here. If you make it too machine parsable, then it's not very human readable, and vice versa. The user ID field has been a RFC-(2)822 for more or less forever, and a key (even a key intended for special non-common purposes) that doesn't have such a user ID will cause confusion. Instead, however, I recommend you define a new User Attribute type. This is a user ID alternative that is part of the OpenPGP spec but is not restricted to text, or indeed, any particular format. Up til now the only defined user attribute has been "image" (used to attach a picture to a key), but if you define a "TLS" or "server" type, you can have exactly the semantics you desire without interfering with the regular user ID. David From owner-ietf-openpgp@mail.imc.org Fri Jul 25 08:47:37 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5832328C1FA for ; Fri, 25 Jul 2008 08:47:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 Adv3ZyBlt2hq for ; Fri, 25 Jul 2008 08:47:36 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 62B8428C1F2 for ; Fri, 25 Jul 2008 08:47:36 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PFE8SY093892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 08:14:08 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PFE8CR093891; Fri, 25 Jul 2008 08:14:08 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PFE7a0093883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Jul 2008 08:14:07 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 444D4FF26C for ; Sat, 26 Jul 2008 01:14:06 +1000 (EST) Message-ID: <4889EDBA.9030008@e164.org> Date: Sat, 26 Jul 2008 01:14:02 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> In-Reply-To: <20080725144129.GA10490@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > Allow me to suggest that overloading the user ID field in such a > drastic manner may not be the best way to go here. If you make it too > machine parsable, then it's not very human readable, and vice versa. > The user ID field has been a RFC-(2)822 for more or less forever, and > a key (even a key intended for special non-common purposes) that > doesn't have such a user ID will cause confusion. If used for server purposes I doubt it will cause confusion, and such keys should not be used for email. > Instead, however, I recommend you define a new User Attribute type. > This is a user ID alternative that is part of the OpenPGP spec but is > not restricted to text, or indeed, any particular format. Up til now > the only defined user attribute has been "image" (used to attach a > picture to a key), but if you define a "TLS" or "server" type, you can > have exactly the semantics you desire without interfering with the > regular user ID. Is there any problem with defining several types, ie town/city, state/province, country etc? Of course there would be a definite need for a 'DNS' or hostname type. This would of course be more computer friendly, and there should be no reason for any user id at all to be on these keys. -- Best regards, Duane From owner-ietf-openpgp@mail.imc.org Fri Jul 25 09:17:02 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 663A23A69B6 for ; Fri, 25 Jul 2008 09:17:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 lApzV72HmIHU for ; Fri, 25 Jul 2008 09:17:01 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 92D473A6838 for ; Fri, 25 Jul 2008 09:17:01 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PFu5jX097652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 08:56:05 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PFu57b097651; Fri, 25 Jul 2008 08:56: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.14.2/8.14.2) with ESMTP id m6PFu3Yx097644 for ; Fri, 25 Jul 2008 08:56:04 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.jabberwocky.com (c-75-69-177-157.hsd1.ma.comcast.net [75.69.177.157]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id m6PFu2k06978 for ; Fri, 25 Jul 2008 11:56:02 -0400 Received: from jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.jabberwocky.com (8.14.1/8.14.1) with SMTP id m6PFtvNk011147 for ; Fri, 25 Jul 2008 11:55:57 -0400 Date: Fri, 25 Jul 2008 11:55:57 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes Message-ID: <20080725155557.GA10710@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4889EDBA.9030008@e164.org> OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.18 (2008-05-17) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Sat, Jul 26, 2008 at 01:14:02AM +1000, Duane wrote: > > David Shaw wrote: > > > Allow me to suggest that overloading the user ID field in such a > > drastic manner may not be the best way to go here. If you make it too > > machine parsable, then it's not very human readable, and vice versa. > > The user ID field has been a RFC-(2)822 for more or less forever, and > > a key (even a key intended for special non-common purposes) that > > doesn't have such a user ID will cause confusion. > > If used for server purposes I doubt it will cause confusion, and such > keys should not be used for email. OpenPGP is not an email-only protocol. Inevitably, such a key would leak from the "server" realm to the "everything else" realm. > > Instead, however, I recommend you define a new User Attribute type. > > This is a user ID alternative that is part of the OpenPGP spec but is > > not restricted to text, or indeed, any particular format. Up til now > > the only defined user attribute has been "image" (used to attach a > > picture to a key), but if you define a "TLS" or "server" type, you can > > have exactly the semantics you desire without interfering with the > > regular user ID. > > Is there any problem with defining several types, ie town/city, > state/province, country etc? No. You can define anything you like, in any form you like. Basically, think of it as being given a chunk of bytes attached to an OpenPGP key. You can put anything you want in there, in any format you want, to be parsed however you want. You completely own the format. OpenPGP then guarantees that your bytes cannot be tampered with, using the same protection that it uses for regular user ID strings. David From owner-ietf-openpgp@mail.imc.org Fri Jul 25 17:04:34 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E2B03A6820 for ; Fri, 25 Jul 2008 17:04:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 ISEvDcdFoCa4 for ; Fri, 25 Jul 2008 17:04:33 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 4C3933A67D4 for ; Fri, 25 Jul 2008 17:04:32 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PNfIaV030715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 16:41:18 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PNfIia030714; Fri, 25 Jul 2008 16:41:18 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PNfHrS030708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Jul 2008 16:41:18 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 2E434FF26C for ; Sat, 26 Jul 2008 09:41:18 +1000 (EST) Message-ID: <488A6496.4070606@e164.org> Date: Sat, 26 Jul 2008 09:41:10 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> In-Reply-To: <20080725155557.GA10710@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > OpenPGP is not an email-only protocol. Inevitably, such a key would > leak from the "server" realm to the "everything else" realm. X.509 prevented this by usage extensions in the certificates stating what it should and shouldn't be allowed to do, and also preventing it from being used for some purposes. However I most certainly am not suggesting or implying in any way shape or form that things go down that path with OpenPGP. Protecting people from themselves has been detrimental and possibly limited innovation and thinking on the topic because everyone seems to think the same way when it comes to implementing X.509. > No. You can define anything you like, in any form you like. > Basically, think of it as being given a chunk of bytes attached to an > OpenPGP key. You can put anything you want in there, in any format > you want, to be parsed however you want. You completely own the > format. OpenPGP then guarantees that your bytes cannot be tampered > with, using the same protection that it uses for regular user ID > strings. This is why I posted to this list, because I didn't know if I was doing things in the best way or not, and I appreciate pointing out things I didn't consider. I'll re-write the draft, if someone hasn't already, to incorporate these new ideas. -- Best regards, Duane From owner-ietf-openpgp@mail.imc.org Fri Jul 25 21:52:02 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C8503A6923 for ; Fri, 25 Jul 2008 21:52:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 fTeXW7ndg6qr for ; Fri, 25 Jul 2008 21:52:02 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id EAAAA3A67EB for ; Fri, 25 Jul 2008 21:52:01 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6Q4PnCl046092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 21:25:50 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6Q4PnJh046091; Fri, 25 Jul 2008 21:25:49 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6Q4PgVB046081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Jul 2008 21:25:49 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 50987FF26C for ; Sat, 26 Jul 2008 14:25:45 +1000 (EST) Message-ID: <488AA73B.8050704@e164.org> Date: Sat, 26 Jul 2008 14:25:31 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> In-Reply-To: <20080725155557.GA10710@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > No. You can define anything you like, in any form you like. > Basically, think of it as being given a chunk of bytes attached to an > OpenPGP key. You can put anything you want in there, in any format > you want, to be parsed however you want. You completely own the > format. OpenPGP then guarantees that your bytes cannot be tampered > with, using the same protection that it uses for regular user ID > strings. I'm stuck at this point. If I specify to use multiple types I'm not sure how to easily group the additional information to particular hostnames or wildcards. Would anyone have any suggestions at this point in time? -- Best regards, Duane From owner-ietf-openpgp@mail.imc.org Sat Jul 26 07:27:35 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 254093A6A4F for ; Sat, 26 Jul 2008 07:27:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 T3n+u+qD6LPx for ; Sat, 26 Jul 2008 07:27:34 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 52D973A6878 for ; Sat, 26 Jul 2008 07:27:34 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QE5CVn081071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 07:05:12 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6QE5CuG081070; Sat, 26 Jul 2008 07:05:12 -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.14.2/8.14.2) with ESMTP id m6QE5AIN081062 for ; Sat, 26 Jul 2008 07:05:11 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.jabberwocky.com (c-75-69-177-157.hsd1.ma.comcast.net [75.69.177.157]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id m6QE59k13684 for ; Sat, 26 Jul 2008 10:05:09 -0400 Received: from [172.24.84.28] (grover.jabberwocky.com [172.24.84.28]) by walrus.jabberwocky.com (8.14.1/8.14.1) with ESMTP id m6QE5400016876 for ; Sat, 26 Jul 2008 10:05:04 -0400 Message-Id: <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> From: David Shaw To: OpenPGP In-Reply-To: <488AA73B.8050704@e164.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Subject: Re: Standardisation of User ID usage for Server Purposes Date: Sat, 26 Jul 2008 10:05:03 -0400 References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> X-Mailer: Apple Mail (2.926) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Jul 26, 2008, at 12:25 AM, Duane wrote: > > David Shaw wrote: > >> No. You can define anything you like, in any form you like. >> Basically, think of it as being given a chunk of bytes attached to an >> OpenPGP key. You can put anything you want in there, in any format >> you want, to be parsed however you want. You completely own the >> format. OpenPGP then guarantees that your bytes cannot be tampered >> with, using the same protection that it uses for regular user ID >> strings. > > I'm stuck at this point. If I specify to use multiple types I'm not > sure > how to easily group the additional information to particular hostnames > or wildcards. > > Would anyone have any suggestions at this point in time? I'm not suggesting you define multiple OpenPGP user attribute packets. Just one. Inside that single blob of bytes, you can break it up however you want. Heck, you can define it as text and use the exact same format you were discussing before if you like. David From owner-ietf-openpgp@mail.imc.org Sat Jul 26 09:20:55 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA5C43A6AC3 for ; Sat, 26 Jul 2008 09:20:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 HpgyiVBwdRit for ; Sat, 26 Jul 2008 09:20:54 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id C0EE13A67A7 for ; Sat, 26 Jul 2008 09:20:54 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QFvXwD089957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 08:57:33 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6QFvXP8089956; Sat, 26 Jul 2008 08:57:33 -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 an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QFvVC4089948 for ; Sat, 26 Jul 2008 08:57:33 -0700 (MST) (envelope-from buanzo@buanzo.com.ar) Received: by an-out-0708.google.com with SMTP id c35so805683anc.44 for ; Sat, 26 Jul 2008 08:57:31 -0700 (PDT) Received: by 10.100.57.6 with SMTP id f6mr2574509ana.115.1217087850924; Sat, 26 Jul 2008 08:57:30 -0700 (PDT) Received: from ?10.10.0.4? ( [201.235.164.113]) by mx.google.com with ESMTPS id 9sm5868613yws.5.2008.07.26.08.57.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 26 Jul 2008 08:57:29 -0700 (PDT) Message-ID: <488B4964.7090604@buanzo.com.ar> Date: Sat, 26 Jul 2008 12:57:24 -0300 From: "Arturo 'Buanzo' Busleiman" Organization: GNU/Buanzo User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: David Shaw CC: OpenPGP Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> In-Reply-To: <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=6857704D Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 David Shaw wrote: | I'm not suggesting you define multiple OpenPGP user attribute packets. | Just one. Inside that single blob of bytes, you can break it up however | you want. Heck, you can define it as text and use the exact same format | you were discussing before if you like. I'd like to see some server-usage related options in an openpgp key. It'd be very useful for Enigform / mod_openpgp. ( http://maotest.buanzo.org and http://wiki.buanzo.org for more details). - -- Arturo "Buanzo" Busleiman Independent Linux and Security Consultant - SANS - OISSG - OWASP http://www.buanzo.com.ar/pro/eng.html Mailing List Archives at http://archiver.mailfighter.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIi0ljAlpOsGhXcE0RClZRAJ9kFxhYxPGSWk7sykiSQuuJKmlKuACaAvZZ qoSO8SWrPJXy5yhKz7TCAMg= =c6UB -----END PGP SIGNATURE----- From owner-ietf-openpgp@mail.imc.org Sat Jul 26 16:04:13 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1600D3A67FE for ; Sat, 26 Jul 2008 16:04:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 21kMq2mrqIL2 for ; Sat, 26 Jul 2008 16:04:12 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 5CF523A67E3 for ; Sat, 26 Jul 2008 16:04:12 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QMd87j012800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 15:39:08 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6QMd88D012799; Sat, 26 Jul 2008 15:39:08 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QMd70S012792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 26 Jul 2008 15:39:08 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 25AA1FF26C for ; Sun, 27 Jul 2008 08:39:08 +1000 (EST) Message-ID: <488BA777.50606@e164.org> Date: Sun, 27 Jul 2008 08:38:47 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> <488B4964.7090604@buanzo.com.ar> In-Reply-To: <488B4964.7090604@buanzo.com.ar> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Arturo 'Buanzo' Busleiman wrote: > I'd like to see some server-usage related options in an openpgp key. So would I, that's why I started this topic in the first place ;) -- Best regards, Duane From owner-ietf-openpgp@mail.imc.org Sat Jul 26 16:05:21 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CB933A67FE for ; Sat, 26 Jul 2008 16:05:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 6RqI9SwW8nRR for ; Sat, 26 Jul 2008 16:05:20 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id A567D3A67E3 for ; Sat, 26 Jul 2008 16:05:20 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QMgIY6012955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 15:42:19 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6QMgIGx012954; Sat, 26 Jul 2008 15:42:18 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QMgIPs012948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 26 Jul 2008 15:42:18 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id E7E34FF26C for ; Sun, 27 Jul 2008 08:42:19 +1000 (EST) Message-ID: <488BA838.1000503@e164.org> Date: Sun, 27 Jul 2008 08:42:00 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> In-Reply-To: <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > I'm not suggesting you define multiple OpenPGP user attribute packets. > Just one. Inside that single blob of bytes, you can break it up however > you want. Heck, you can define it as text and use the exact same format > you were discussing before if you like. In hindsight it doesn't seem like the best way to do it, I guess I have just answered my question over night, the additional information can be grouped by the key they are attached to, and if some other organisation has other hostnames that should be a separate key, and OpenPGP key dumps can contain multiple keys so that really solves that unless I've overlooked something fundamental? -- Best regards, Duane From owner-ietf-openpgp@mail.imc.org Sat Jul 26 17:32:24 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 674B63A684A for ; Sat, 26 Jul 2008 17:32:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.505 X-Spam-Level: X-Spam-Status: No, score=-1.505 tagged_above=-999 required=5 tests=[AWL=-0.541, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, URIBL_RHS_DOB=1.083] 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 SB17Oc9tNU0o for ; Sat, 26 Jul 2008 17:32:23 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 8D2FB3A6825 for ; Sat, 26 Jul 2008 17:32:23 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6R0DmKw017741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 17:13:48 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6R0Dmt7017740; Sat, 26 Jul 2008 17:13:48 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6R0DlTI017734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 26 Jul 2008 17:13:48 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 427FEFF26C for ; Sun, 27 Jul 2008 10:13:49 +1000 (EST) Message-ID: <488BBDA5.7080905@e164.org> Date: Sun, 27 Jul 2008 10:13:25 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Draft Update X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Ok, I've made some updates, firstly removing specific references to DNS since this is no longer specifically mean to be for DNS and I've other changes to remove references to using the user id field, and instead using user attributes to have the information in a format much more suitable for computers, this makes more sense to me than a blob of string doesn't need to be split up and parsed to extract the information. http://open-pgp.info/wiki/index.php?title=Standardisation_of_OpenPGP_Keys_for_Server_Purposes Is there anything I've missed or overlooked at all? -- Best regards, Duane From owner-ietf-openpgp@mail.imc.org Sat Jul 26 17:57:54 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 529DF3A684A for ; Sat, 26 Jul 2008 17:57:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 Kt3B8H33mLoe for ; Sat, 26 Jul 2008 17:57:53 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 752433A63C9 for ; Sat, 26 Jul 2008 17:57:53 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6R0bEss018837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 17:37:14 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6R0bEx1018836; Sat, 26 Jul 2008 17:37: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 wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.227]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6R0bDBj018829 for ; Sat, 26 Jul 2008 17:37:13 -0700 (MST) (envelope-from buanzo@buanzo.com.ar) Received: by wr-out-0506.google.com with SMTP id 50so3279354wri.2 for ; Sat, 26 Jul 2008 17:37:13 -0700 (PDT) Received: by 10.90.90.4 with SMTP id n4mr4806410agb.74.1217119032513; Sat, 26 Jul 2008 17:37:12 -0700 (PDT) Received: from ?10.10.0.4? ( [201.235.164.113]) by mx.google.com with ESMTPS id 6sm6561470ywi.1.2008.07.26.17.37.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 26 Jul 2008 17:37:11 -0700 (PDT) Message-ID: <488BC32D.2030202@buanzo.com.ar> Date: Sat, 26 Jul 2008 21:37:01 -0300 From: "Arturo 'Buanzo' Busleiman" Organization: GNU/Buanzo User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Duane CC: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> <488B4964.7090604@buanzo.com.ar> <488BA777.50606@e164.org> In-Reply-To: <488BA777.50606@e164.org> X-Enigmail-Version: 0.95.6 OpenPGP: id=6857704D Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Duane wrote: | So would I, that's why I started this topic in the first place ;) Yeah, sure, I mean, I'm ++1 on your idea :) - Anyway, I really look forward to a nice draft on the idea! :) - -- Arturo "Buanzo" Busleiman Independent Linux and Security Consultant - SANS - OISSG - OWASP http://www.buanzo.com.ar/pro/eng.html Mailing List Archives at http://archiver.mailfighter.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIi8MtAlpOsGhXcE0RCjkQAJ92eguGqXSAORXkzeTS9dTKPHFQLACcD9aC l2q5hR9D0RsPvBFF5W/m5p0= =WShG -----END PGP SIGNATURE----- From owner-ietf-openpgp@mail.imc.org Mon Jul 28 10:17:06 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87BEE28C240 for ; Mon, 28 Jul 2008 10:17:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.631 X-Spam-Level: X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[AWL=-0.668, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, URIBL_RHS_DOB=1.083] 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 SZ8WueS57IKe for ; Mon, 28 Jul 2008 10:17:05 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 473BF28C221 for ; Mon, 28 Jul 2008 10:17:05 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SGuJbk077663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jul 2008 09:56:19 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6SGuJNQ077662; Mon, 28 Jul 2008 09:56:19 -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 [66.93.68.160]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SGuE9Q077648 for ; Mon, 28 Jul 2008 09:56:19 -0700 (MST) (envelope-from jon@callas.org) Received: from keys.merrymeet.com (keys.merrymeet.com [66.93.68.161]) (Authenticated sender: jon) by merrymeet.com (Postfix) with ESMTP id 8725C119A190 for ; Mon, 28 Jul 2008 09:56:13 -0700 (PDT) Received: from titania.merrymeet.com ([66.93.68.165]) by keys.merrymeet.com (PGP Universal service); Mon, 28 Jul 2008 09:56:11 -0700 X-PGP-Universal: processed; by keys.merrymeet.com on Mon, 28 Jul 2008 09:56:11 -0700 Cc: ietf-openpgp@imc.org Message-Id: <8E36DDE7-1297-4661-8171-B59F85F97AAD@callas.org> From: Jon Callas To: Duane In-Reply-To: <488BBDA5.7080905@e164.org> Mime-Version: 1.0 (Apple Message framework v928.1) Subject: Re: Draft Update Date: Mon, 28 Jul 2008 09:56:11 -0700 References: <488BBDA5.7080905@e164.org> X-Mailer: Apple Mail (2.928.1) X-PGP-Encoding-Format: Partitioned X-PGP-Encoding-Version: 2.0.2 X-Content-PGP-Universal-Saved-Content-Transfer-Encoding: 7bit X-Content-PGP-Universal-Saved-Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 26, 2008, at 5:13 PM, Duane wrote: > > > Ok, I've made some updates, firstly removing specific references to =20 > DNS > since this is no longer specifically mean to be for DNS and I've other > changes to remove references to using the user id field, and instead > using user attributes to have the information in a format much more > suitable for computers, this makes more sense to me than a blob of > string doesn't need to be split up and parsed to extract the =20 > information. > > http://open-pgp.info/wiki/index.php?title=3DStandardisation_of_OpenPGP_Ke= ys_for_Server_Purposes > > Is there anything I've missed or overlooked at all? I don't think it was necessary to get rid of all of the user id uses. =20 RFC 4880 and 2440 were carefully explicit. Here's the 4880 language: 5.11. User ID Packet (Tag 13) A User ID packet consists of UTF-8 text that is intended to =20 represent the name and email address of the key holder. By convention, it includes an RFC 2822 [RFC2822] mail name-addr, but there are no restrictions on its content. The packet length in the header specifies the length of the User ID. Note the words "intended" and "by convention." Also, "... but there =20 are no restrictions on its content." The discussion on this is similar to a discussion as to whether =20 someone should put DNS information in a new RR or in a TXT record. =20 Yes, it's probably better in some respect to expand the user =20 attributes, but there's nothing wrong with just putting the text in =20 there, especially since there's all this existing code that can =20 display it correctly. There are plenty of cases where a User ID contains nothing but =20 descriptive text ("XYZ Corp Security Alert Signing Key") or non-email =20 names like an X.509 Distinguished Name. I agree with people who say that a User Attribute packet is better in =20 a pure sense. However, the downside of that is that new UAs need =20 setting/getting/display code. Just dropping the text in a UID packet =20 is clunkier, but works everywhere. Knowing when to use which is merely wisdom. Jon -----BEGIN PGP SIGNATURE----- Version: PGP Universal 2.6.3 Charset: US-ASCII wj8DBQFIjforsTedWZOD3gYRAnbEAJsH5XH8aSKWYhaItUNtrkqdSKjRuQCg6oSE 2AVFXqFIqxmDetuw11aSfEQ=3D =3D0rGp -----END PGP SIGNATURE----- From owner-ietf-openpgp@mail.imc.org Mon Jul 28 11:00:45 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F00028C267 for ; Mon, 28 Jul 2008 11:00:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 u4JVOUJ6whYS for ; Mon, 28 Jul 2008 11:00:44 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 519BC28C1C6 for ; Mon, 28 Jul 2008 11:00:44 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SHgcdo082248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jul 2008 10:42:38 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6SHgcc4082247; Mon, 28 Jul 2008 10:42:38 -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.14.2/8.14.2) with ESMTP id m6SHgWBX082227 for ; Mon, 28 Jul 2008 10:42:38 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.jabberwocky.com (c-75-69-177-157.hsd1.ma.comcast.net [75.69.177.157]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id m6SHgVk29270 for ; Mon, 28 Jul 2008 13:42:31 -0400 Received: from jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.jabberwocky.com (8.14.1/8.14.1) with SMTP id m6SHgQYm001569 for ; Mon, 28 Jul 2008 13:42:26 -0400 Date: Mon, 28 Jul 2008 13:42:26 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: Re: Draft Update Message-ID: <20080728174226.GB31483@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org References: <488BBDA5.7080905@e164.org> <8E36DDE7-1297-4661-8171-B59F85F97AAD@callas.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8E36DDE7-1297-4661-8171-B59F85F97AAD@callas.org> OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.18 (2008-05-17) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Mon, Jul 28, 2008 at 09:56:11AM -0700, Jon Callas wrote: > There are plenty of cases where a User ID contains nothing but > descriptive text ("XYZ Corp Security Alert Signing Key") or non-email > names like an X.509 Distinguished Name. > > I agree with people who say that a User Attribute packet is better in > a pure sense. However, the downside of that is that new UAs need > setting/getting/display code. Just dropping the text in a UID packet > is clunkier, but works everywhere. Indeed, but since a key must have at least one "real" UID packet, a UA can only be additional information on top of that. That's why I advise that people doing complex multi field (as in this example) and non-textual things just make a UA - that way, the required UID can be displayed by all the existing code so the key isn't quasi-anonymous, but at the same time the new info doesn't have to create hard to read UIDs full of quoting characters and the like. I'm not sure it's easier to pack and unpack multi field data into a text string (with quoting, etc) than it would be to just define a structure that you own completely. David From owner-ietf-openpgp@mail.imc.org Mon Jul 28 14:08:04 2008 Return-Path: X-Original-To: ietfarch-openpgp-archive@core3.amsl.com Delivered-To: ietfarch-openpgp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 35EED3A6B25 for ; Mon, 28 Jul 2008 14:08:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.969 X-Spam-Level: X-Spam-Status: No, score=-1.969 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 hiqkuqAGC2Qd for ; Mon, 28 Jul 2008 14:08:03 -0700 (PDT) Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 56C2F3A6B1F for ; Mon, 28 Jul 2008 14:08:03 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SKdAhm098279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jul 2008 13:39:15 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6SKdAfg098278; Mon, 28 Jul 2008 13:39:10 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SKd9WC098271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 28 Jul 2008 13:39:10 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 7DFBCFF26C for ; Tue, 29 Jul 2008 06:39:10 +1000 (EST) Message-ID: <488E2E5C.7070406@e164.org> Date: Tue, 29 Jul 2008 06:38:52 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Draft Update References: <488BBDA5.7080905@e164.org> <8E36DDE7-1297-4661-8171-B59F85F97AAD@callas.org> <20080728174226.GB31483@jabberwocky.com> In-Reply-To: <20080728174226.GB31483@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > On Mon, Jul 28, 2008 at 09:56:11AM -0700, Jon Callas wrote: > >> There are plenty of cases where a User ID contains nothing but >> descriptive text ("XYZ Corp Security Alert Signing Key") or non-email >> names like an X.509 Distinguished Name. >> >> I agree with people who say that a User Attribute packet is better in >> a pure sense. However, the downside of that is that new UAs need >> setting/getting/display code. Just dropping the text in a UID packet >> is clunkier, but works everywhere. > > Indeed, but since a key must have at least one "real" UID packet, a UA > can only be additional information on top of that. That's why I > advise that people doing complex multi field (as in this example) and > non-textual things just make a UA - that way, the required UID can be > displayed by all the existing code so the key isn't quasi-anonymous, > but at the same time the new info doesn't have to create hard to read > UIDs full of quoting characters and the like. > > I'm not sure it's easier to pack and unpack multi field data into a > text string (with quoting, etc) than it would be to just define a > structure that you own completely. I agree with the practicality side of things that just using the UID field because it works already, no software changes needed etc, on the other hand I agree with David's sentiments about trying to stuff complex multi-field information into a single string. Because nothing exists already when it comes to server uses we have an opportunity to do things right and we shouldn't do things the easy way just because it will be the easiest to implement at this point in time, that's how X.509 got into a bit of a mess, we should learn from the mistakes they made rather then making them over again. Currently the draft I've written doesn't use the User ID field at all for anything, however if one real UID must exist per key then what should it be? I don't think it should be hostnames, simply because there could be more than one and X.509 has a bit of a mess with that, it could be the person or organisations name I suppose, since that information should be unique on a per key basis. In any case I'm more than open to suggestions on what to do here, however we have information that PKIX didn't have. -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SKdAhm098279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jul 2008 13:39:15 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6SKdAfg098278; Mon, 28 Jul 2008 13:39:10 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SKd9WC098271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 28 Jul 2008 13:39:10 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 7DFBCFF26C for ; Tue, 29 Jul 2008 06:39:10 +1000 (EST) Message-ID: <488E2E5C.7070406@e164.org> Date: Tue, 29 Jul 2008 06:38:52 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Draft Update References: <488BBDA5.7080905@e164.org> <8E36DDE7-1297-4661-8171-B59F85F97AAD@callas.org> <20080728174226.GB31483@jabberwocky.com> In-Reply-To: <20080728174226.GB31483@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > On Mon, Jul 28, 2008 at 09:56:11AM -0700, Jon Callas wrote: > >> There are plenty of cases where a User ID contains nothing but >> descriptive text ("XYZ Corp Security Alert Signing Key") or non-email >> names like an X.509 Distinguished Name. >> >> I agree with people who say that a User Attribute packet is better in >> a pure sense. However, the downside of that is that new UAs need >> setting/getting/display code. Just dropping the text in a UID packet >> is clunkier, but works everywhere. > > Indeed, but since a key must have at least one "real" UID packet, a UA > can only be additional information on top of that. That's why I > advise that people doing complex multi field (as in this example) and > non-textual things just make a UA - that way, the required UID can be > displayed by all the existing code so the key isn't quasi-anonymous, > but at the same time the new info doesn't have to create hard to read > UIDs full of quoting characters and the like. > > I'm not sure it's easier to pack and unpack multi field data into a > text string (with quoting, etc) than it would be to just define a > structure that you own completely. I agree with the practicality side of things that just using the UID field because it works already, no software changes needed etc, on the other hand I agree with David's sentiments about trying to stuff complex multi-field information into a single string. Because nothing exists already when it comes to server uses we have an opportunity to do things right and we shouldn't do things the easy way just because it will be the easiest to implement at this point in time, that's how X.509 got into a bit of a mess, we should learn from the mistakes they made rather then making them over again. Currently the draft I've written doesn't use the User ID field at all for anything, however if one real UID must exist per key then what should it be? I don't think it should be hostnames, simply because there could be more than one and X.509 has a bit of a mess with that, it could be the person or organisations name I suppose, since that information should be unique on a per key basis. In any case I'm more than open to suggestions on what to do here, however we have information that PKIX didn't have. -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SHgcdo082248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jul 2008 10:42:38 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6SHgcc4082247; Mon, 28 Jul 2008 10:42:38 -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.14.2/8.14.2) with ESMTP id m6SHgWBX082227 for ; Mon, 28 Jul 2008 10:42:38 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.jabberwocky.com (c-75-69-177-157.hsd1.ma.comcast.net [75.69.177.157]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id m6SHgVk29270 for ; Mon, 28 Jul 2008 13:42:31 -0400 Received: from jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.jabberwocky.com (8.14.1/8.14.1) with SMTP id m6SHgQYm001569 for ; Mon, 28 Jul 2008 13:42:26 -0400 Date: Mon, 28 Jul 2008 13:42:26 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: Re: Draft Update Message-ID: <20080728174226.GB31483@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org References: <488BBDA5.7080905@e164.org> <8E36DDE7-1297-4661-8171-B59F85F97AAD@callas.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8E36DDE7-1297-4661-8171-B59F85F97AAD@callas.org> OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.18 (2008-05-17) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Mon, Jul 28, 2008 at 09:56:11AM -0700, Jon Callas wrote: > There are plenty of cases where a User ID contains nothing but > descriptive text ("XYZ Corp Security Alert Signing Key") or non-email > names like an X.509 Distinguished Name. > > I agree with people who say that a User Attribute packet is better in > a pure sense. However, the downside of that is that new UAs need > setting/getting/display code. Just dropping the text in a UID packet > is clunkier, but works everywhere. Indeed, but since a key must have at least one "real" UID packet, a UA can only be additional information on top of that. That's why I advise that people doing complex multi field (as in this example) and non-textual things just make a UA - that way, the required UID can be displayed by all the existing code so the key isn't quasi-anonymous, but at the same time the new info doesn't have to create hard to read UIDs full of quoting characters and the like. I'm not sure it's easier to pack and unpack multi field data into a text string (with quoting, etc) than it would be to just define a structure that you own completely. David Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SGuJbk077663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jul 2008 09:56:19 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6SGuJNQ077662; Mon, 28 Jul 2008 09:56:19 -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 [66.93.68.160]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6SGuE9Q077648 for ; Mon, 28 Jul 2008 09:56:19 -0700 (MST) (envelope-from jon@callas.org) Received: from keys.merrymeet.com (keys.merrymeet.com [66.93.68.161]) (Authenticated sender: jon) by merrymeet.com (Postfix) with ESMTP id 8725C119A190 for ; Mon, 28 Jul 2008 09:56:13 -0700 (PDT) Received: from titania.merrymeet.com ([66.93.68.165]) by keys.merrymeet.com (PGP Universal service); Mon, 28 Jul 2008 09:56:11 -0700 X-PGP-Universal: processed; by keys.merrymeet.com on Mon, 28 Jul 2008 09:56:11 -0700 Cc: ietf-openpgp@imc.org Message-Id: <8E36DDE7-1297-4661-8171-B59F85F97AAD@callas.org> From: Jon Callas To: Duane In-Reply-To: <488BBDA5.7080905@e164.org> Mime-Version: 1.0 (Apple Message framework v928.1) Subject: Re: Draft Update Date: Mon, 28 Jul 2008 09:56:11 -0700 References: <488BBDA5.7080905@e164.org> X-Mailer: Apple Mail (2.928.1) X-PGP-Encoding-Format: Partitioned X-PGP-Encoding-Version: 2.0.2 X-Content-PGP-Universal-Saved-Content-Transfer-Encoding: 7bit X-Content-PGP-Universal-Saved-Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 26, 2008, at 5:13 PM, Duane wrote: > > > Ok, I've made some updates, firstly removing specific references to =20 > DNS > since this is no longer specifically mean to be for DNS and I've other > changes to remove references to using the user id field, and instead > using user attributes to have the information in a format much more > suitable for computers, this makes more sense to me than a blob of > string doesn't need to be split up and parsed to extract the =20 > information. > > http://open-pgp.info/wiki/index.php?title=3DStandardisation_of_OpenPGP_Ke= ys_for_Server_Purposes > > Is there anything I've missed or overlooked at all? I don't think it was necessary to get rid of all of the user id uses. =20 RFC 4880 and 2440 were carefully explicit. Here's the 4880 language: 5.11. User ID Packet (Tag 13) A User ID packet consists of UTF-8 text that is intended to =20 represent the name and email address of the key holder. By convention, it includes an RFC 2822 [RFC2822] mail name-addr, but there are no restrictions on its content. The packet length in the header specifies the length of the User ID. Note the words "intended" and "by convention." Also, "... but there =20 are no restrictions on its content." The discussion on this is similar to a discussion as to whether =20 someone should put DNS information in a new RR or in a TXT record. =20 Yes, it's probably better in some respect to expand the user =20 attributes, but there's nothing wrong with just putting the text in =20 there, especially since there's all this existing code that can =20 display it correctly. There are plenty of cases where a User ID contains nothing but =20 descriptive text ("XYZ Corp Security Alert Signing Key") or non-email =20 names like an X.509 Distinguished Name. I agree with people who say that a User Attribute packet is better in =20 a pure sense. However, the downside of that is that new UAs need =20 setting/getting/display code. Just dropping the text in a UID packet =20 is clunkier, but works everywhere. Knowing when to use which is merely wisdom. Jon -----BEGIN PGP SIGNATURE----- Version: PGP Universal 2.6.3 Charset: US-ASCII wj8DBQFIjforsTedWZOD3gYRAnbEAJsH5XH8aSKWYhaItUNtrkqdSKjRuQCg6oSE 2AVFXqFIqxmDetuw11aSfEQ=3D =3D0rGp -----END PGP SIGNATURE----- Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6R0bEss018837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 17:37:14 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6R0bEx1018836; Sat, 26 Jul 2008 17:37: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 wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.227]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6R0bDBj018829 for ; Sat, 26 Jul 2008 17:37:13 -0700 (MST) (envelope-from buanzo@buanzo.com.ar) Received: by wr-out-0506.google.com with SMTP id 50so3279354wri.2 for ; Sat, 26 Jul 2008 17:37:13 -0700 (PDT) Received: by 10.90.90.4 with SMTP id n4mr4806410agb.74.1217119032513; Sat, 26 Jul 2008 17:37:12 -0700 (PDT) Received: from ?10.10.0.4? ( [201.235.164.113]) by mx.google.com with ESMTPS id 6sm6561470ywi.1.2008.07.26.17.37.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 26 Jul 2008 17:37:11 -0700 (PDT) Message-ID: <488BC32D.2030202@buanzo.com.ar> Date: Sat, 26 Jul 2008 21:37:01 -0300 From: "Arturo 'Buanzo' Busleiman" Organization: GNU/Buanzo User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Duane CC: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> <488B4964.7090604@buanzo.com.ar> <488BA777.50606@e164.org> In-Reply-To: <488BA777.50606@e164.org> X-Enigmail-Version: 0.95.6 OpenPGP: id=6857704D Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Duane wrote: | So would I, that's why I started this topic in the first place ;) Yeah, sure, I mean, I'm ++1 on your idea :) - Anyway, I really look forward to a nice draft on the idea! :) - -- Arturo "Buanzo" Busleiman Independent Linux and Security Consultant - SANS - OISSG - OWASP http://www.buanzo.com.ar/pro/eng.html Mailing List Archives at http://archiver.mailfighter.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIi8MtAlpOsGhXcE0RCjkQAJ92eguGqXSAORXkzeTS9dTKPHFQLACcD9aC l2q5hR9D0RsPvBFF5W/m5p0= =WShG -----END PGP SIGNATURE----- Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6R0DmKw017741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 17:13:48 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6R0Dmt7017740; Sat, 26 Jul 2008 17:13:48 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6R0DlTI017734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 26 Jul 2008 17:13:48 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 427FEFF26C for ; Sun, 27 Jul 2008 10:13:49 +1000 (EST) Message-ID: <488BBDA5.7080905@e164.org> Date: Sun, 27 Jul 2008 10:13:25 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Draft Update X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Ok, I've made some updates, firstly removing specific references to DNS since this is no longer specifically mean to be for DNS and I've other changes to remove references to using the user id field, and instead using user attributes to have the information in a format much more suitable for computers, this makes more sense to me than a blob of string doesn't need to be split up and parsed to extract the information. http://open-pgp.info/wiki/index.php?title=Standardisation_of_OpenPGP_Keys_for_Server_Purposes Is there anything I've missed or overlooked at all? -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QMgIY6012955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 15:42:19 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6QMgIGx012954; Sat, 26 Jul 2008 15:42:18 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QMgIPs012948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 26 Jul 2008 15:42:18 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id E7E34FF26C for ; Sun, 27 Jul 2008 08:42:19 +1000 (EST) Message-ID: <488BA838.1000503@e164.org> Date: Sun, 27 Jul 2008 08:42:00 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> In-Reply-To: <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > I'm not suggesting you define multiple OpenPGP user attribute packets. > Just one. Inside that single blob of bytes, you can break it up however > you want. Heck, you can define it as text and use the exact same format > you were discussing before if you like. In hindsight it doesn't seem like the best way to do it, I guess I have just answered my question over night, the additional information can be grouped by the key they are attached to, and if some other organisation has other hostnames that should be a separate key, and OpenPGP key dumps can contain multiple keys so that really solves that unless I've overlooked something fundamental? -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QMd87j012800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 15:39:08 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6QMd88D012799; Sat, 26 Jul 2008 15:39:08 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QMd70S012792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 26 Jul 2008 15:39:08 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 25AA1FF26C for ; Sun, 27 Jul 2008 08:39:08 +1000 (EST) Message-ID: <488BA777.50606@e164.org> Date: Sun, 27 Jul 2008 08:38:47 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> <488B4964.7090604@buanzo.com.ar> In-Reply-To: <488B4964.7090604@buanzo.com.ar> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Arturo 'Buanzo' Busleiman wrote: > I'd like to see some server-usage related options in an openpgp key. So would I, that's why I started this topic in the first place ;) -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QFvXwD089957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 08:57:33 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6QFvXP8089956; Sat, 26 Jul 2008 08:57:33 -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 an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QFvVC4089948 for ; Sat, 26 Jul 2008 08:57:33 -0700 (MST) (envelope-from buanzo@buanzo.com.ar) Received: by an-out-0708.google.com with SMTP id c35so805683anc.44 for ; Sat, 26 Jul 2008 08:57:31 -0700 (PDT) Received: by 10.100.57.6 with SMTP id f6mr2574509ana.115.1217087850924; Sat, 26 Jul 2008 08:57:30 -0700 (PDT) Received: from ?10.10.0.4? ( [201.235.164.113]) by mx.google.com with ESMTPS id 9sm5868613yws.5.2008.07.26.08.57.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 26 Jul 2008 08:57:29 -0700 (PDT) Message-ID: <488B4964.7090604@buanzo.com.ar> Date: Sat, 26 Jul 2008 12:57:24 -0300 From: "Arturo 'Buanzo' Busleiman" Organization: GNU/Buanzo User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: David Shaw CC: OpenPGP Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> In-Reply-To: <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=6857704D Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 David Shaw wrote: | I'm not suggesting you define multiple OpenPGP user attribute packets. | Just one. Inside that single blob of bytes, you can break it up however | you want. Heck, you can define it as text and use the exact same format | you were discussing before if you like. I'd like to see some server-usage related options in an openpgp key. It'd be very useful for Enigform / mod_openpgp. ( http://maotest.buanzo.org and http://wiki.buanzo.org for more details). - -- Arturo "Buanzo" Busleiman Independent Linux and Security Consultant - SANS - OISSG - OWASP http://www.buanzo.com.ar/pro/eng.html Mailing List Archives at http://archiver.mailfighter.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIi0ljAlpOsGhXcE0RClZRAJ9kFxhYxPGSWk7sykiSQuuJKmlKuACaAvZZ qoSO8SWrPJXy5yhKz7TCAMg= =c6UB -----END PGP SIGNATURE----- Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6QE5CVn081071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jul 2008 07:05:12 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6QE5CuG081070; Sat, 26 Jul 2008 07:05:12 -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.14.2/8.14.2) with ESMTP id m6QE5AIN081062 for ; Sat, 26 Jul 2008 07:05:11 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.jabberwocky.com (c-75-69-177-157.hsd1.ma.comcast.net [75.69.177.157]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id m6QE59k13684 for ; Sat, 26 Jul 2008 10:05:09 -0400 Received: from [172.24.84.28] (grover.jabberwocky.com [172.24.84.28]) by walrus.jabberwocky.com (8.14.1/8.14.1) with ESMTP id m6QE5400016876 for ; Sat, 26 Jul 2008 10:05:04 -0400 Message-Id: <4AACFE9B-A518-4B62-BD2B-A281D7F1D842@jabberwocky.com> From: David Shaw To: OpenPGP In-Reply-To: <488AA73B.8050704@e164.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Subject: Re: Standardisation of User ID usage for Server Purposes Date: Sat, 26 Jul 2008 10:05:03 -0400 References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> <488AA73B.8050704@e164.org> X-Mailer: Apple Mail (2.926) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Jul 26, 2008, at 12:25 AM, Duane wrote: > > David Shaw wrote: > >> No. You can define anything you like, in any form you like. >> Basically, think of it as being given a chunk of bytes attached to an >> OpenPGP key. You can put anything you want in there, in any format >> you want, to be parsed however you want. You completely own the >> format. OpenPGP then guarantees that your bytes cannot be tampered >> with, using the same protection that it uses for regular user ID >> strings. > > I'm stuck at this point. If I specify to use multiple types I'm not > sure > how to easily group the additional information to particular hostnames > or wildcards. > > Would anyone have any suggestions at this point in time? I'm not suggesting you define multiple OpenPGP user attribute packets. Just one. Inside that single blob of bytes, you can break it up however you want. Heck, you can define it as text and use the exact same format you were discussing before if you like. David Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6Q4PnCl046092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 21:25:50 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6Q4PnJh046091; Fri, 25 Jul 2008 21:25:49 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6Q4PgVB046081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Jul 2008 21:25:49 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 50987FF26C for ; Sat, 26 Jul 2008 14:25:45 +1000 (EST) Message-ID: <488AA73B.8050704@e164.org> Date: Sat, 26 Jul 2008 14:25:31 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> In-Reply-To: <20080725155557.GA10710@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > No. You can define anything you like, in any form you like. > Basically, think of it as being given a chunk of bytes attached to an > OpenPGP key. You can put anything you want in there, in any format > you want, to be parsed however you want. You completely own the > format. OpenPGP then guarantees that your bytes cannot be tampered > with, using the same protection that it uses for regular user ID > strings. I'm stuck at this point. If I specify to use multiple types I'm not sure how to easily group the additional information to particular hostnames or wildcards. Would anyone have any suggestions at this point in time? -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PNfIaV030715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 16:41:18 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PNfIia030714; Fri, 25 Jul 2008 16:41:18 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PNfHrS030708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Jul 2008 16:41:18 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 2E434FF26C for ; Sat, 26 Jul 2008 09:41:18 +1000 (EST) Message-ID: <488A6496.4070606@e164.org> Date: Sat, 26 Jul 2008 09:41:10 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> <20080725155557.GA10710@jabberwocky.com> In-Reply-To: <20080725155557.GA10710@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > OpenPGP is not an email-only protocol. Inevitably, such a key would > leak from the "server" realm to the "everything else" realm. X.509 prevented this by usage extensions in the certificates stating what it should and shouldn't be allowed to do, and also preventing it from being used for some purposes. However I most certainly am not suggesting or implying in any way shape or form that things go down that path with OpenPGP. Protecting people from themselves has been detrimental and possibly limited innovation and thinking on the topic because everyone seems to think the same way when it comes to implementing X.509. > No. You can define anything you like, in any form you like. > Basically, think of it as being given a chunk of bytes attached to an > OpenPGP key. You can put anything you want in there, in any format > you want, to be parsed however you want. You completely own the > format. OpenPGP then guarantees that your bytes cannot be tampered > with, using the same protection that it uses for regular user ID > strings. This is why I posted to this list, because I didn't know if I was doing things in the best way or not, and I appreciate pointing out things I didn't consider. I'll re-write the draft, if someone hasn't already, to incorporate these new ideas. -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PFu5jX097652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 08:56:05 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PFu57b097651; Fri, 25 Jul 2008 08:56: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.14.2/8.14.2) with ESMTP id m6PFu3Yx097644 for ; Fri, 25 Jul 2008 08:56:04 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.jabberwocky.com (c-75-69-177-157.hsd1.ma.comcast.net [75.69.177.157]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id m6PFu2k06978 for ; Fri, 25 Jul 2008 11:56:02 -0400 Received: from jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.jabberwocky.com (8.14.1/8.14.1) with SMTP id m6PFtvNk011147 for ; Fri, 25 Jul 2008 11:55:57 -0400 Date: Fri, 25 Jul 2008 11:55:57 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes Message-ID: <20080725155557.GA10710@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> <4889EDBA.9030008@e164.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4889EDBA.9030008@e164.org> OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.18 (2008-05-17) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Sat, Jul 26, 2008 at 01:14:02AM +1000, Duane wrote: > > David Shaw wrote: > > > Allow me to suggest that overloading the user ID field in such a > > drastic manner may not be the best way to go here. If you make it too > > machine parsable, then it's not very human readable, and vice versa. > > The user ID field has been a RFC-(2)822 for more or less forever, and > > a key (even a key intended for special non-common purposes) that > > doesn't have such a user ID will cause confusion. > > If used for server purposes I doubt it will cause confusion, and such > keys should not be used for email. OpenPGP is not an email-only protocol. Inevitably, such a key would leak from the "server" realm to the "everything else" realm. > > Instead, however, I recommend you define a new User Attribute type. > > This is a user ID alternative that is part of the OpenPGP spec but is > > not restricted to text, or indeed, any particular format. Up til now > > the only defined user attribute has been "image" (used to attach a > > picture to a key), but if you define a "TLS" or "server" type, you can > > have exactly the semantics you desire without interfering with the > > regular user ID. > > Is there any problem with defining several types, ie town/city, > state/province, country etc? No. You can define anything you like, in any form you like. Basically, think of it as being given a chunk of bytes attached to an OpenPGP key. You can put anything you want in there, in any format you want, to be parsed however you want. You completely own the format. OpenPGP then guarantees that your bytes cannot be tampered with, using the same protection that it uses for regular user ID strings. David Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PFE8SY093892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 08:14:08 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PFE8CR093891; Fri, 25 Jul 2008 08:14:08 -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.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PFE7a0093883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Jul 2008 08:14:07 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 444D4FF26C for ; Sat, 26 Jul 2008 01:14:06 +1000 (EST) Message-ID: <4889EDBA.9030008@e164.org> Date: Sat, 26 Jul 2008 01:14:02 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes References: <4889C456.6020001@e164.org> <20080725144129.GA10490@jabberwocky.com> In-Reply-To: <20080725144129.GA10490@jabberwocky.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: David Shaw wrote: > Allow me to suggest that overloading the user ID field in such a > drastic manner may not be the best way to go here. If you make it too > machine parsable, then it's not very human readable, and vice versa. > The user ID field has been a RFC-(2)822 for more or less forever, and > a key (even a key intended for special non-common purposes) that > doesn't have such a user ID will cause confusion. If used for server purposes I doubt it will cause confusion, and such keys should not be used for email. > Instead, however, I recommend you define a new User Attribute type. > This is a user ID alternative that is part of the OpenPGP spec but is > not restricted to text, or indeed, any particular format. Up til now > the only defined user attribute has been "image" (used to attach a > picture to a key), but if you define a "TLS" or "server" type, you can > have exactly the semantics you desire without interfering with the > regular user ID. Is there any problem with defining several types, ie town/city, state/province, country etc? Of course there would be a definite need for a 'DNS' or hostname type. This would of course be more computer friendly, and there should be no reason for any user id at all to be on these keys. -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PEfbLx090453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 07:41:38 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PEfbQb090452; Fri, 25 Jul 2008 07:41:37 -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.14.2/8.14.2) with ESMTP id m6PEfaXb090443 for ; Fri, 25 Jul 2008 07:41:37 -0700 (MST) (envelope-from dshaw@jabberwocky.com) Received: from walrus.jabberwocky.com (c-75-69-177-157.hsd1.ma.comcast.net [75.69.177.157]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id m6PEfYk06509 for ; Fri, 25 Jul 2008 10:41:35 -0400 Received: from jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.jabberwocky.com (8.14.1/8.14.1) with SMTP id m6PEfTjS010688 for ; Fri, 25 Jul 2008 10:41:29 -0400 Date: Fri, 25 Jul 2008 10:41:29 -0400 From: David Shaw To: ietf-openpgp@imc.org Subject: Re: Standardisation of User ID usage for Server Purposes Message-ID: <20080725144129.GA10490@jabberwocky.com> Mail-Followup-To: ietf-openpgp@imc.org References: <4889C456.6020001@e164.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4889C456.6020001@e164.org> OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc User-Agent: Mutt/1.5.18 (2008-05-17) Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Fri, Jul 25, 2008 at 10:17:26PM +1000, Duane wrote: > > > While I'm happy to see that TLS usage was extended to include OpenPGP > usage, and I mean no disrespect at all, but the author did not include > any details on the structure or formatting of the User ID for server > purposes other than to include the hostname in a single User ID. > > This no better than X.509 in some respects as it didn't mention anything > about allowing for multiple hostnames, how wild card hostnames should be > treated or how miscellaneous information could be presented or used. > > I think it's crucial that if people want to adopt or use OpenPGP in > place of X.509 that all these things must be addressed and standardised. Allow me to suggest that overloading the user ID field in such a drastic manner may not be the best way to go here. If you make it too machine parsable, then it's not very human readable, and vice versa. The user ID field has been a RFC-(2)822 for more or less forever, and a key (even a key intended for special non-common purposes) that doesn't have such a user ID will cause confusion. Instead, however, I recommend you define a new User Attribute type. This is a user ID alternative that is part of the OpenPGP spec but is not restricted to text, or indeed, any particular format. Up til now the only defined user attribute has been "image" (used to attach a picture to a key), but if you define a "TLS" or "server" type, you can have exactly the semantics you desire without interfering with the regular user ID. David Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PCIDvc077230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2008 05:18:13 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6PCIDK8077229; Fri, 25 Jul 2008 05:18: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 mail.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6PCI5AE077214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Jul 2008 05:18:13 -0700 (MST) (envelope-from duane@e164.org) Received: from [192.168.100.244] (dsl-48-19.qld1.net.au [125.168.48.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTPSA id 921A0FF26C for ; Fri, 25 Jul 2008 22:18:05 +1000 (EST) Message-ID: <4889C456.6020001@e164.org> Date: Fri, 25 Jul 2008 22:17:26 +1000 From: Duane User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: ietf-openpgp@imc.org Subject: Standardisation of User ID usage for Server Purposes X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: While I'm happy to see that TLS usage was extended to include OpenPGP usage, and I mean no disrespect at all, but the author did not include any details on the structure or formatting of the User ID for server purposes other than to include the hostname in a single User ID. This no better than X.509 in some respects as it didn't mention anything about allowing for multiple hostnames, how wild card hostnames should be treated or how miscellaneous information could be presented or used. I think it's crucial that if people want to adopt or use OpenPGP in place of X.509 that all these things must be addressed and standardised. Please forgive my presumptions on this topic a little, I have had a lot more exposure to X.509 in the past and even running a public CA so I have a little bit of experience when it comes to the kind of things people want included in certificates, or at least what they've come to expect already. To give you a little bit of background where I'm coming from specifically here, I am already trying to submit a draft through the DNSEXT working group to incorporate encryption of DNS servers, not just authentication and originally I had written up a single draft that covered both the topic of DNS encryption and using OpenPGP keys for servers. I have since split this draft into two separate drafts and would love nothing more then to get some comments, suggestions, feedbacks, anything on my proposal, or even if I could get it adopted by this working group. Since splitting my draft it's too rough to be presentable just yet in a normal internet draft form, however that shouldn't take more than a few days, until then the rough outline is viewable here: http://open-pgp.info/wiki/index.php?title=Standardisation_of_Information_in_OpenPGP_User_IDs_for_Server_Purposes -- Best regards, Duane Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m676OrCN080896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Jul 2008 23:24:54 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m676Orvu080895; Sun, 6 Jul 2008 23:24:53 -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 brainhub.org (h-66-134-92-50.snvacaid.covad.net [66.134.92.50]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m676Op7G080888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 6 Jul 2008 23:24:53 -0700 (MST) (envelope-from openpgp@brainhub.org) Received: from localhost.localdomain ([192.168.0.141]) by brainhub.org (8.14.2/8.14.1) with ESMTP id m676OoCX008988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 6 Jul 2008 23:24:51 -0700 Message-ID: <4871B6B2.2000709@brainhub.org> Date: Sun, 06 Jul 2008 23:24:50 -0700 From: Andrey Jivsov User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: OpenPGP Subject: Re: New Version Notification for draft-jivsov-openpgp-ecc-01 References: <20080707060332.013FB3A68A8@core3.amsl.com> In-Reply-To: <20080707060332.013FB3A68A8@core3.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-openpgp@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: > I will wait until at least July 6 before submitting this as a second > revisions of the draft to IETF. As promised, the *-01.txt revision is now available: IETF I-D Submission Tool wrote: > A new version of I-D, draft-jivsov-openpgp-ecc-01.txt has been successfuly submitted by Andrey Jivsov and posted to the IETF repository. > > Filename: draft-jivsov-openpgp-ecc > Revision: 01 > Title: ECC in OpenPGP > Creation_date: 2008-07-06 > WG ID: Independent Submission > Number_of_pages: 14 > > Abstract: > This document proposes an Elliptic Curve Cryptography extension to > the OpenPGP public key format and specifies three Elliptic Curves > that enjoy broad support by other standards, including NIST > standards. The document aims to standardize an optimal but narrow > set of parameters for best interoperability and it does so within > the framework it defines that can be expanded in the future to > allow more choices. > > Conventions used in this document > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in > this document are to be interpreted as described in [RFC2119]. > An application MAY implement this draft; note that any [RFC2119] > keyword within this draft applies to an OpenPGP application only if > it chooses to implement this draft. > > > > The IETF Secretariat. All revisions that we discussed so far in HTML, PDF, and TXT formats are available at http://brainhub.googlepages.com/pgp .