From owner-ietf-smime@mail.imc.org Tue Dec 2 16:00:25 2003 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10495 for ; Tue, 2 Dec 2003 16:00:24 -0500 (EST) Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB2KbOib045212 for ; Tue, 2 Dec 2003 12:37:24 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hB2KbOuh045209 for ietf-smime-bks; Tue, 2 Dec 2003 12:37:24 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB2KbMib045196 for ; Tue, 2 Dec 2003 12:37:22 -0800 (PST) (envelope-from dinaras@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08932; Tue, 2 Dec 2003 15:36:35 -0500 (EST) Message-Id: <200312022036.PAA08932@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-smime@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-smime-pss-02.txt Date: Tue, 02 Dec 2003 15:36:35 -0500 Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the S/MIME Mail Security Working Group of the IETF. Title : Use of the PSS Signature Algorithm in CMS Author(s) : J. Schaad Filename : draft-ietf-smime-pss-02.txt Pages : 5 Date : 2003-12-2 This document specifies the conventions for using the RSA Probabilistic Signature Scheme (RSASSA-PSS) digital signature algorithm [P1v2.1] with the Cryptographic Message Syntax (CMS) [CMS]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-smime-pss-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-smime-pss-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-12-2154649.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-smime-pss-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-smime-pss-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-12-2154649.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-smime@mail.imc.org Wed Dec 3 18:16:42 2003 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15415 for ; Wed, 3 Dec 2003 18:16:41 -0500 (EST) Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB3Ms7ib086942 for ; Wed, 3 Dec 2003 14:54:07 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hB3Ms7Rl086941 for ietf-smime-bks; Wed, 3 Dec 2003 14:54:07 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from brutesquadlabs.com (gtec136-m.isomedia.com [207.115.67.136] (may be forged)) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB3Ms6ib086935 for ; Wed, 3 Dec 2003 14:54:07 -0800 (PST) (envelope-from blake@brutesquadlabs.com) Received: from DEXTER ([192.168.0.6]) by brutesquadlabs.com with ESMTP ; Wed, 3 Dec 2003 14:54:03 -0800 From: "Blake Ramsdell" To: Subject: WG LAST CALL: draft-ietf-smime-pss-02.txt Date: Wed, 3 Dec 2003 14:54:03 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit This message initiates an SMIME Working Group Last Call on the document: Title : Use of the PSS Signature Algorithm in CMS Author(s) : J. Schaad Filename : draft-ietf-smime-pss-02.txt Pages : 5 Date : 2003-12-2 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-02.txt The purpose of this WG Last Call is to ensure that the Working Group has achieved consensus that the document is suitable for publication as a Proposed Standard. Please review the document for both technical and editorial problems. Technical issues should be discussed on this list. Editorial issues may be sent to the document editor. The Last Call period will end on Wednesday, December 10, 2003. Upon completion of the last call, the WG chairs will take action based upon the consensus of the WG. Possible actions include: 1) recommending to the IETF Security Area Directors that the document, after possible editorial or other minor changes, be considered by the IESG for publication as a Standard Track RFC (which generally involves an IETF-wide Last Call); or 2) requiring that outstanding issues be adequately addressed prior to further action (including, possibly, another WG Last Call). Remember that it is our responsibility as Working Group members to ensure the quality of our documents and of the Internet Standards process. So, please read and comment! Blake -- Blake Ramsdell | Brute Squad Labs | http://www.brutesquadlabs.com From rx1srww@aol.com Fri Dec 5 01:43:11 2003 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09313 for ; Fri, 5 Dec 2003 01:43:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AS9gR-00034F-00 for smime-archive@ietf.org; Fri, 05 Dec 2003 01:43:23 -0500 Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AS9gQ-00033U-00 for smime-archive@ietf.org; Fri, 05 Dec 2003 01:43:22 -0500 Received: from 81-202-21-12.user.ono.com ([81.202.21.12]) by manatick with smtp (Exim 4.24) id 1AS9Qd-0003CL-3p for smime-archive@ietf.org; Fri, 05 Dec 2003 01:27:04 -0500 Received: from [63.42.103.179] by 81-202-21-12.user.ono.com; Fri, 05 Dec 2003 03:22:53 +0200 Message-ID: From: "Josue Field" Reply-To: "Josue Field" To: Subject: Whats been happening? Date: Fri, 05 Dec 03 03:22:53 GMT X-Mailer: AOL 7.0 for Windows US sub 118 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=".1_C02272B..." X-Priority: 3 X-MSMail-Priority: Normal --.1_C02272B... Content-Type: text/html; Content-Transfer-Encoding: quoted-printable

 


D<= !-- blister -->O YOU WANT A MORTGAGE FROM ONLY 1.5% ?

If you are in t= he market for a mortgage, look for further than us for the lowest rates ava<= !-- concurred -->ilable!

Our risk-free, no obligat= ion ratefinder software can help= you find the l= owest mortg= age regardless of your financial si<= !-- recitative -->tuation!

Click here for your FREE risk-free, no= obligation quote!

 

 

You are recievin= g this email because you are a mem= ber at free= raffle.us.
We have your signup and confirmation ip on file! G= et off here
Please allow upt<= !-- covet -->o 7 days to be removed.

=

ick Here For Information




here if you would not like to r= eceive future mailings.

--69FF4FCED6AD3A.3E8ED_-- From u32ywb@aol.com Mon Dec 29 04:28:49 2003 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21294 for ; Mon, 29 Dec 2003 04:28:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aathg-0006m5-00 for smime-archive@ietf.org; Mon, 29 Dec 2003 04:28:48 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aatfv-0006Xh-00 for smime-archive@ietf.org; Mon, 29 Dec 2003 04:26:59 -0500 Received: from cpe-069-133-012-169.cinci.rr.com ([69.133.12.169]) by ietf-mx with smtp (Exim 4.12) id 1Aatdc-0006LJ-00; Mon, 29 Dec 2003 04:24:40 -0500 Received: from (HELO tfuiv7) [91.158.142.208] by cpe-069-133-012-169.cinci.rr.com; Mon, 29 Dec 2003 06:26:14 +0200 Message-ID: <58$1$n--x-g1gm6g1$$6v2ahg1rxz78@8oj.bx64lq> From: "Beatriz Ramirez" Reply-To: "Beatriz Ramirez" To: , , , , , , , , , , , , , , , Subject: Learn to make a fortune on eBay! Date: Mon, 29 Dec 03 06:26:14 GMT X-Mailer: AOL 7.0 for Windows US sub 118 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="D.CDA541C.E2F." X-Priority: 3 X-MSMail-Priority: Normal X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=16.7 required=5.0 tests=BIZ_TLD,CLICK_BELOW, DATE_SPAMWARE_Y2K,FORGED_AOL_HTML,HTML_60_70,HTML_FONTCOLOR_RED, HTML_FONT_INVISIBLE,HTML_IMAGE_ONLY_04,HTML_MESSAGE, MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI, MISSING_MIMEOLE,MISSING_OUTLOOK_NAME,OBFUSCATING_COMMENT autolearn=no version=2.60 X-Spam-Report: * 4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting * 0.1 HTML_60_70 BODY: Message is 60% to 70% HTML * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.4 HTML_FONT_INVISIBLE BODY: HTML font color is same as background * 0.1 HTML_FONTCOLOR_RED BODY: HTML font color is red * 1.5 HTML_IMAGE_ONLY_04 BODY: HTML: images with 200-400 bytes of words * 0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset * 0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain * 1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE * 0.0 CLICK_BELOW Asks you to click below * 1.8 FORGED_AOL_HTML AOL can't send HTML message only * 1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts * 4.3 OBFUSCATING_COMMENT HTML comments which obfuscate text * 0.1 MISSING_OUTLOOK_NAME Message looks like Outlook, but isn't --D.CDA541C.E2F. Content-Type: text/html; Content-Transfer-Encoding: quoted-printable order confirmation. your order should be sh= ipped by January, via fedex. your federal express tracking number is piccolo.
thank you for registering. your userid is: remote

Learn to Make A Fortune With Ebay!
Complete Turnkey System
Software - Videos - Turo= rials
Click Here For Information




here if you would not like to r= eceive future mailings.

--D.CDA541C.E2F.-- From qdors@el-nacional.com Tue Dec 30 18:34:32 2003 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18725 for ; Tue, 30 Dec 2003 18:34:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AbTNZ-000557-00 for smime-archive@ietf.org; Tue, 30 Dec 2003 18:34:25 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbTK1-0004Jd-00 for smime-archive@ietf.org; Tue, 30 Dec 2003 18:30:46 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AbTG4-0003UX-00 for smime-archive@ietf.org; Tue, 30 Dec 2003 18:26:40 -0500 Received: from h197n1c1o1037.bredband.skanova.com ([81.227.32.197]) by mx2.foretec.com with smtp (Exim 4.24) id 1AbTG5-0001nL-Ag for smime-archive@ietf.org; Tue, 30 Dec 2003 18:26:41 -0500 Received: from [81.227.32.197] by e-hostzz.netIP with HTTP; Tue, 30 Dec 2003 04:23:16 -0700 From: "Morgan Estrada" To: smime-archive@ietf.org Subject: Re: EVNZSN, the western hill Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [e-hostzz.netIP] Date: Tue, 30 Dec 2003 15:27:16 +0400 Reply-To: "Morgan" Content-Type: multipart/alternative; boundary="--ALT--RYYL41782538685695 " Message-Id: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=HTML_IMAGE_ONLY_10, HTML_MESSAGE autolearn=no version=2.60 ----ALT--RYYL41782538685695 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit desecrater mosque pleura grievance was quickie rung slight crayon reflect sauce cyclic air corpse bulrush crematory indistinct stigma citric molecule skyway ----ALT--RYYL41782538685695 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 8bit

Free Cable* TV

consecutive capella band headstrong downward blight rocky ingratiate teletype mannequin vicinal sonora vermin decal masonic sinistral essence survive covariant guide pauline quarantine domesticate rabble theta burr admissible oligarchy came arsenide errol berenices dollop indecomposable cramp bivalve lackey grimaldi
centaur taketh lie iowa ambulant pulitzer grow hebe codon anaerobic big levity photolysis barbarous quixotic blake chianti historiography quaint adamant aerodynamic dominick countrymen jerky cadent sedimentary besotted cane raceway diabase d'etat christy fearsome area
----ALT--RYYL41782538685695 -- ----ALT--RYYL41782538685695-- ----ALT--RYYL41782538685695 -- From seytwdb@el-nacional.com Wed Dec 31 18:06:13 2003 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28603 for ; Wed, 31 Dec 2003 18:06:13 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AbpPl-0003g4-00 for smime-archive@ietf.org; Wed, 31 Dec 2003 18:06:09 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbpON-0003ei-00 for smime-archive@ietf.org; Wed, 31 Dec 2003 18:04:46 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AbpLU-0003dV-00 for smime-archive@ietf.org; Wed, 31 Dec 2003 18:01:44 -0500 Received: from adsl-67-118-113-125.dsl.snfc21.pacbell.net ([67.118.113.125]) by mx2.foretec.com with smtp (Exim 4.24) id 1AbpL5-0004Gx-7d for smime-archive@ietf.org; Wed, 31 Dec 2003 18:01:19 -0500 Received: from [67.118.113.125] by e-hostzz.netIP with HTTP; Wed, 31 Dec 2003 15:49:57 -0700 From: "Wayne Sizemore" To: smime-archive@ietf.org Subject: Re: GPKS, persons the scope Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [e-hostzz.netIP] Date: Wed, 31 Dec 2003 18:49:57 -0400 Reply-To: "Wayne" Content-Type: multipart/alternative; boundary="--ALT--VZOI52943198895385" Message-Id: ----ALT--VZOI52943198895385 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit ahmadabad beast defecate typhus guano bloodhound it'd geochemical shod brevet iq stromberg idiosyncrasy lounsbury veracity ditzel deflate coralline jeopardy obese purport affiance togging boris ----ALT--VZOI52943198895385 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 8bit

Free Cable! TV

marjory curio oracular variegate quantile alterate stopover avenge art corpsman function cochran journey bunt ax dispersible curtsey sumner experience
modish hundredfold capsule phlox buckle halley grizzle grandchild anemone riparian typo oakland puppet surcease goldwater equivocal bunk elision kitten baffle teat sweetish cabot chiton bachelor elaine queer pedro clergyman yawn folklore
----ALT--VZOI52943198895385-- Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBO4Bqib079617 for ; Tue, 23 Dec 2003 20:11:52 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBO4BqdA079615 for ietf-smime-bks; Tue, 23 Dec 2003 20:11:52 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from smtp.covadmail.net (mx05.covadmail.net [63.65.120.65]) by above.proper.com (8.12.10/8.12.8) with SMTP id hBO4Boib079605 for ; Tue, 23 Dec 2003 20:11:51 -0800 (PST) (envelope-from gary@shortsands.us) Received: (covad.net 7793 invoked from network); 24 Dec 2003 04:11:43 -0000 Received: from unknown (HELO ?10.10.10.14?) (garygriswold@covad.net@66.134.219.34) by sun-qmail13 with SMTP; 24 Dec 2003 04:11:43 -0000 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.0.6 Date: Tue, 23 Dec 2003 23:11:46 -0500 Subject: Requirement: smime for mailto From: Gary Griswold To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: There is a requirement for securing email that was sent as a result of a mailto. When a mailto action is used in conjunction with an HTML form post, most browsers support sending the input values in the body of the message as a URL encoded string. However, they are always transmitted in plain text. Current Microsoft email clients, conceal the data in an attachment where it is not visible to the average user. Unfortunately, this only increases the problem by giving some users the impression that the communication is secure. What is needed is a way to encrypt these emails. Smime provides the means for encryption, but to my knowledge does not provide a means to evoke it during a mailto, or require it for all mailtos. Many reading this might regard this as an HTML problem, because mailto has a history in the HTML specification. But the need here is for a standard that will be implemented into email clients, not browsers. Clicking on a mailto invokes the user's default email client. In RFC 2368 on the Mailto URL scheme, it defines a mailto syntax that includes a list of mail headers as part of the query string of the URL. The grammar is defined as follow: mailtoURL = "mailto:" [ to ] [ headers ] to = #mailbox headers = "?" header * ( "&" header ) header = hname "=" hvalue One possible solution that would not require a change to the mailto specification, is to define a mail header that would invoke encryption of the message. I am interested in this problem, because I have developed a gateway for delivering fully formatted web pages by email. This service is used by low bandwidth users around the world as their primary web access. Information on this service can be found at http://emailweb.us Sincerely yours, Gary Griswold 1 Longfellow Place #3019 Boston, MA 02114 617-694-6403 Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBJMKsib074132 for ; Fri, 19 Dec 2003 14:20:54 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBJMKs4h074131 for ietf-smime-bks; Fri, 19 Dec 2003 14:20:54 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBJMKrib074126 for ; Fri, 19 Dec 2003 14:20:53 -0800 (PST) (envelope-from jimsch@nwlink.com) Received: from ROMANS (ip237.132.dial-acs01.sea.iinet.com [209.20.132.237]) by smtp2.pacifier.net (Postfix) with ESMTP id D0C8E6A5AF; Fri, 19 Dec 2003 14:20:53 -0800 (PST) Reply-To: From: "Jim Schaad" To: "Sean P. Turner" , "Blake Ramsdell" Cc: Subject: RE: I-D ACTION:draft-ietf-smime-pss-03.txt Date: Fri, 19 Dec 2003 14:24:27 -0800 Message-ID: <00ac01c3c67e$ddff9780$1400a8c0@augustcellars.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <200312192045.PAA25902@ietf.org> Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Sean & Blake, The changes necessary to address the comments of Russ and Burt have been made. The document should now be ready to forward to the Area Directors. jim > -----Original Message----- > From: owner-ietf-smime@mail.imc.org > [mailto:owner-ietf-smime@mail.imc.org] On Behalf Of > Internet-Drafts@ietf.org > Sent: Friday, December 19, 2003 12:46 PM > To: IETF-Announce: > Cc: ietf-smime@imc.org > Subject: I-D ACTION:draft-ietf-smime-pss-03.txt > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. This draft is a work item of the > S/MIME Mail Security Working Group of the IETF. > > Title : Use of the PSS Signature Algorithm in CMS > Author(s) : J. Schaad > Filename : draft-ietf-smime-pss-03.txt > Pages : 6 > Date : 2003-12-19 > > This document specifies the conventions for using the RSA > Probabilistic Signature Scheme (RSASSA-PSS) digital signature > algorithm [P1v2.1] with the Cryptographic Message Syntax (CMS). > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-03.tx t To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-smime-pss-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-smime-pss-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBJKjuib068948 for ; Fri, 19 Dec 2003 12:45:56 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBJKjuHp068947 for ietf-smime-bks; Fri, 19 Dec 2003 12:45:56 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBJKjrib068941 for ; Fri, 19 Dec 2003 12:45:55 -0800 (PST) (envelope-from dinaras@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25902; Fri, 19 Dec 2003 15:45:52 -0500 (EST) Message-Id: <200312192045.PAA25902@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-smime@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-smime-pss-03.txt Date: Fri, 19 Dec 2003 15:45:50 -0500 Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the S/MIME Mail Security Working Group of the IETF. Title : Use of the PSS Signature Algorithm in CMS Author(s) : J. Schaad Filename : draft-ietf-smime-pss-03.txt Pages : 6 Date : 2003-12-19 This document specifies the conventions for using the RSA Probabilistic Signature Scheme (RSASSA-PSS) digital signature algorithm [P1v2.1] with the Cryptographic Message Syntax (CMS). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-03.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-smime-pss-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-smime-pss-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-12-19145704.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-smime-pss-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-smime-pss-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-12-19145704.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBBLSRib095665 for ; Thu, 11 Dec 2003 13:28:27 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBBLSR4f095664 for ietf-smime-bks; Thu, 11 Dec 2003 13:28:27 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from mail11.atl.registeredsite.com (nobody@mail11.atl.registeredsite.com [64.224.219.85]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBBLSPib095658 for ; Thu, 11 Dec 2003 13:28:26 -0800 (PST) (envelope-from egerck@nma.com) Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122]) by mail11.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id hBBLSNt7013013; Thu, 11 Dec 2003 16:28:23 -0500 Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Thu, 11 Dec 2003 15:28:21 -0600 Message-ID: <3FD8E16A.B2152F65@nma.com> Date: Thu, 11 Dec 2003 13:28:10 -0800 From: Ed Gerck X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Robert E. Frank" CC: internet-payments , IETF-SMIME List Subject: Re: Digital Signatures for Corporate Voting and or Proxy Submissions? References: <002701c3bfb7$e465c0e0$0301a8c0@sbcglobal.net> Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Robert,

It is possible and legal in California and in at least other 20 US states. In fact, one
of the first was California's Intel. Safevote, for example, has done more than
35 legally binding elections in the US -- including nonprofit associations. Please
ask your attorney to contact me for additional info.

Cheers,
Ed Gerck

"Robert E. Frank" wrote:

We have used PKI for many years and we want to embed its use it throughout the operations of a new, nonprofit corporation we are forming. In addition to authorizing PKI applications for typical enterprise interchange purposes, we want to specify in the articles of incorporation and in the corporate by-laws that PKI-based applications will be authorized for corporate management applications. For example, when Directors and Members can not personally attend annual or special corporate meetings, we want to allow the use of PKI-based  applications to vote, submit proxies, and to remotely conduct other confidential corporate management processes. However, my attorney advises the current California Corporations Code does not authorize the use of PKI-protected applications for corporate director and membership voting, proxy submissions, and other corporation management processes. Can anyone be so kind to advise us of specific CA legal authorization for such uses, or to provide us with documentation to confirm that one or more California Corporations are currently authorized to use PKI to digitally protect and enable authentication of corporate membership voting, proxy submissions, and similar functions?  Robert FrankPresidentOpen Commerce, Inc.Pleasanton, CA 94588www.opencommerce.com
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBBFP2ib081432 for ; Thu, 11 Dec 2003 07:25:02 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBBFP2tI081431 for ietf-smime-bks; Thu, 11 Dec 2003 07:25:02 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from woodstock.binhost.com (woodstock.binhost.com [144.202.240.3]) by above.proper.com (8.12.10/8.12.8) with SMTP id hBBFP0ib081415 for ; Thu, 11 Dec 2003 07:25:01 -0800 (PST) (envelope-from housley@vigilsec.com) Received: (qmail 29724 invoked by uid 0); 11 Dec 2003 15:24:33 -0000 Received: from unknown (HELO Russ-Laptop.vigilsec.com) (141.156.167.184) by woodstock.binhost.com with SMTP; 11 Dec 2003 15:24:33 -0000 Message-Id: <5.2.0.9.2.20031211101358.02031fb8@mail.binhost.com> X-Sender: housley@mail.binhost.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Thu, 11 Dec 2003 10:15:18 -0500 To: "Robert E. Frank" From: Russ Housley Subject: Re: Digital Signatures for Corporate Voting and or Proxy Submissions? Cc: ietf-smime@imc.org In-Reply-To: <002701c3bfb7$e465c0e0$0301a8c0@sbcglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I suggest you send mail to ST-ISC@MAIL.ABANET.ORG. The folks on that list are current on legal issues with digital signatures. Russ At 11:24 PM 12/10/2003 -0800, Robert E. Frank wrote: >We have used PKI for many years and we want to embed its use it throughout >the operations of a new, nonprofit corporation we are forming. > >In addition to authorizing PKI applications for typical enterprise >interchange purposes, we want to specify in the articles of incorporation >and in the corporate by-laws that PKI-based applications will be >authorized for corporate management applications. > >For example, when Directors and Members can not personally attend annual >or special corporate meetings, we want to allow the use of >PKI-based applications to vote, submit proxies, and to remotely conduct >other confidential corporate management processes. > >However, my attorney advises the current California Corporations Code does >not authorize the use of PKI-protected applications for corporate director >and membership voting, proxy submissions, and other corporation management >processes. > >Can anyone be so kind to advise us of specific CA legal authorization for >such uses, or to provide us with documentation to confirm that one or more >California Corporations are currently authorized to use PKI to digitally >protect and enable authentication of corporate membership voting, proxy >submissions, and similar functions? > > >Robert Frank >President >Open Commerce, Inc. >Pleasanton, CA 94588 >www.opencommerce.com Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBBEYFib078648 for ; Thu, 11 Dec 2003 06:34:15 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBBEYFxx078647 for ietf-smime-bks; Thu, 11 Dec 2003 06:34:15 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from vulcan.rsasecurity.com (vulcan.rsasecurity.com [204.167.114.130]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBBEYEib078641 for ; Thu, 11 Dec 2003 06:34:15 -0800 (PST) (envelope-from BKaliski@rsasecurity.com) Received: from ebola.securitydynamics.com by vulcan.rsasecurity.com via smtpd (for mail.imc.org [208.184.76.43]) with ESMTP; Thu, 11 Dec 2003 09:34:15 -0500 Received: from sdtihq24.securid.com (localhost [127.0.0.1]) by ebola.securitydynamics.com (8.12.10/NULL) with ESMTP id hBBEY61i016145; Thu, 11 Dec 2003 09:34:06 -0500 (EST) Received: from exna00.securitydynamics.com (exna00.securitydynamics.com [10.100.8.217]) by sdtihq24.securid.com (8.12.10/8.12.9) with ESMTP id hBBEYBsj001261; Thu, 11 Dec 2003 09:34:11 -0500 (EST) Received: by exna00.securitydynamics.com with Internet Mail Service (5.5.2657.72) id ; Thu, 11 Dec 2003 09:33:56 -0500 Message-ID: From: "Kaliski, Burt" To: "'jimsch@exmsft.com'" , "'Blake Ramsdell'" Cc: ietf-smime@imc.org Subject: RE: WG LAST CALL: draft-ietf-smime-pss-02.txt Date: Thu, 11 Dec 2003 09:33:25 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi Jim, I understand the motivation, but the RSASSA-PSS-params specify the full signature process, including the hash. When using RSASSA-PSS in CMS, there are potentially three hashes (not including the one on the mask generation function): 1. hash of eContent 2. hash of signedAttributes 3. hash within PSS padding Hashes 2. and 3. are both part of the RSASSA-PSS signature process. In RSASSA-PSS, hashes 2. and 3. MUST be the same. (This is part of the definition of RSASSA-PSS, not a security requirement per se.) This requirement does not present a problem for a timestamp authority. If the timestamp authority is given only the hash of signedAttributes and the hash algorithm (hash 2.), then the timestamp authority can just select the same hash algorithm within the PSS padding (hash 3.). -- Burt -----Original Message----- From: Jim Schaad [mailto:jimsch@nwlink.com] Sent: Thursday, December 11, 2003 3:55 AM To: Kaliski, Burt; 'Blake Ramsdell' Cc: ietf-smime@imc.org Subject: RE: WG LAST CALL: draft-ietf-smime-pss-02.txt Bert, I wrote this as should since I do not want to rule out the ability for a time stamp authority to be able to sign a message when just the hash and hash algorithm are provided. The two hash functions are in many ways independent, the hash and hash algorithm are really part of the data that is then hashed as part of the signature process. This should refers to the body of the message, producing a hash value that is part of the actual signature processing. jim Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBB8qKib045351 for ; Thu, 11 Dec 2003 00:52:20 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBB8qKKU045350 for ietf-smime-bks; Thu, 11 Dec 2003 00:52:20 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBB8qGib045328 for ; Thu, 11 Dec 2003 00:52:18 -0800 (PST) (envelope-from jimsch@nwlink.com) Received: from ROMANS (ip237.132.dial-acs01.sea.iinet.com [209.20.132.237]) by smtp2.pacifier.net (Postfix) with ESMTP id E1FA16A995; Thu, 11 Dec 2003 00:52:14 -0800 (PST) Reply-To: From: "Jim Schaad" To: "'Kaliski, Burt'" , "'Blake Ramsdell'" Cc: Subject: RE: WG LAST CALL: draft-ietf-smime-pss-02.txt Date: Thu, 11 Dec 2003 00:54:53 -0800 Message-ID: <014f01c3bfc4$71f34750$e1b2efd8@augustcellars.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Bert, I wrote this as should since I do not want to rule out the ability for a time stamp authority to be able to sign a message when just the hash and hash algorithm are provided. The two hash functions are in many ways independent, the hash and hash algorithm are really part of the data that is then hashed as part of the signature process. This should refers to the body of the message, producing a hash value that is part of the actual signature processing. jim > -----Original Message----- > From: owner-ietf-smime@mail.imc.org > [mailto:owner-ietf-smime@mail.imc.org] On Behalf Of Kaliski, Burt > Sent: Wednesday, December 10, 2003 6:58 AM > To: 'Blake Ramsdell' > Cc: ietf-smime@imc.org > Subject: RE: WG LAST CALL: draft-ietf-smime-pss-02.txt > > > > Dear Blake, > > The draft looks good except for one paragraph: > > The same one-way hash function SHOULD be used for computing the > message digest on the signedAttributes and as the hashAlgorithm in > the RSA-PSS-params structure. > > I think the paragraph should say "MUST". > > The id-RSASSA-PSS OID is for the full process of signing a > message, including hashing, padding, and the RSA primitive. > > The RSASSA-PSS-params structure specifies the hash function > that is employed during hashing and padding. The same hash > function is employed in both steps. So, the hash function in > the RSASSA-PSS-params structure MUST be the same as the > message digest algorithm applied to the signedAttributes values. > > (If the signedAttributes are omitted, and the eContent value > is signed directly, then the message digest algorithm that is > applied to the eContent value likewise MUST be the same as > the hash function in the RSASSA-PSS-params structure. I'm not > sure if the eContent-only mode is still supported in CMS, though.) > > id-RSASSA-PSS-params is similar to id-dsa-with-sha1 in that > it specifies the full process of signing a message. It is > different than rsaEncryption, whcih only includes padding and > the RSA primitive, not hashing. This is why it constrains the > message digest algorithm, while rsaEncryption doesn't. > > (Note that the padding step also involves a mask generation > function, which may be based on a hash function. The above > discussion doesn't apply to that hash function; it may or may > not be the same as the hash function applied to the message.) > > -- Burt > > > -----Original Message----- > From: Blake Ramsdell [mailto:blake@brutesquadlabs.com] > Sent: Wednesday, December 03, 2003 5:54 PM > To: ietf-smime@imc.org > Subject: WG LAST CALL: draft-ietf-smime-pss-02.txt > > > > This message initiates an SMIME Working Group Last Call on > the document: > > Title : Use of the PSS Signature Algorithm in CMS > Author(s) : J. Schaad > Filename : draft-ietf-smime-pss-02.txt > Pages : 5 > Date : 2003-12-2 > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-02.tx t The purpose of this WG Last Call is to ensure that the Working Group has achieved consensus that the document is suitable for publication as a Proposed Standard. Please review the document for both technical and editorial problems. Technical issues should be discussed on this list. Editorial issues may be sent to the document editor. The Last Call period will end on Wednesday, December 10, 2003. Upon completion of the last call, the WG chairs will take action based upon the consensus of the WG. Possible actions include: 1) recommending to the IETF Security Area Directors that the document, after possible editorial or other minor changes, be considered by the IESG for publication as a Standard Track RFC (which generally involves an IETF-wide Last Call); or 2) requiring that outstanding issues be adequately addressed prior to further action (including, possibly, another WG Last Call). Remember that it is our responsibility as Working Group members to ensure the quality of our documents and of the Internet Standards process. So, please read and comment! Blake -- Blake Ramsdell | Brute Squad Labs | http://www.brutesquadlabs.com Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBB7NTib018445 for ; Wed, 10 Dec 2003 23:23:29 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBB7NT1V018443 for ietf-smime-bks; Wed, 10 Dec 2003 23:23:29 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from ns1.raydiate.net (www.raydiate.com [64.58.73.42] (may be forged)) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBB7NSib018430 for ; Wed, 10 Dec 2003 23:23:29 -0800 (PST) (envelope-from bobfrank@opencommerce.com) Received: from earth (adsl-67-122-206-117.dsl.snfc21.pacbell.net [67.122.206.117]) by [64.58.73.44] (8.10.2/8.10.2) with SMTP id hBB73ux11308; Thu, 11 Dec 2003 02:03:57 -0500 Message-ID: <002701c3bfb7$e465c0e0$0301a8c0@sbcglobal.net> Reply-To: "Robert E. Frank" From: "Robert E. Frank" To: "internet-payments" , "IETF-SMIME List" Subject: Digital Signatures for Corporate Voting and or Proxy Submissions? Date: Wed, 10 Dec 2003 23:24:48 -0800 Organization: Open Commerce, Inc. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0024_01C3BF74.CDF98820" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_0024_01C3BF74.CDF98820 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We have used PKI for many years and we want to embed its use it = throughout the operations of a new, nonprofit corporation we are = forming. =20 In addition to authorizing PKI applications for typical enterprise = interchange purposes, we want to specify in the articles of = incorporation and in the corporate by-laws that PKI-based applications = will be authorized for corporate management applications. =20 For example, when Directors and Members can not personally attend annual = or special corporate meetings, we want to allow the use of PKI-based = applications to vote, submit proxies, and to remotely conduct other = confidential corporate management processes. However, my attorney advises the current California Corporations Code = does not authorize the use of PKI-protected applications for corporate = director and membership voting, proxy submissions, and other corporation = management processes. Can anyone be so kind to advise us of specific CA legal authorization = for such uses, or to provide us with documentation to confirm that one = or more California Corporations are currently authorized to use PKI to = digitally protect and enable authentication of corporate membership = voting, proxy submissions, and similar functions? Robert Frank President Open Commerce, Inc. Pleasanton, CA 94588 www.opencommerce.com ------=_NextPart_000_0024_01C3BF74.CDF98820 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
We have used PKI for many years = and we want to=20 embed its use it throughout the operations of a new,=20 nonprofit corporation we are forming. 
 
In addition to authorizing PKI = applications for=20 typical enterprise interchange purposes, we want to specify in the = articles=20 of incorporation and in the corporate by-laws that PKI-based = applications will=20 be authorized for corporate management applications.   =
 
For example, when Directors and Members = can not=20 personally attend annual or special corporate meetings, we want to=20 allow the use of PKI-based  applications to vote, submit = proxies, and=20 to remotely conduct other confidential corporate management=20 processes.
 
However, my=20 attorney advises the current California Corporations Code does not = authorize the=20 use of PKI-protected applications for corporate director and membership = voting,=20 proxy submissions, and other corporation management = processes.
 
Can anyone be so kind to advise us of = specific CA=20 legal authorization for such uses, or to provide us with=20 documentation to confirm that one or more California = Corporations are=20 currently authorized to use PKI to digitally protect = and=20 enable authentication of corporate membership voting, proxy=20 submissions, and similar functions?
 
 
Robert Frank
President
Open Commerce, Inc.
Pleasanton, CA 94588
www.opencommerce.com ------=_NextPart_000_0024_01C3BF74.CDF98820-- Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBAFoRib042750 for ; Wed, 10 Dec 2003 07:50:27 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBAFoRFB042749 for ietf-smime-bks; Wed, 10 Dec 2003 07:50:27 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from outbound1.sopragroup.com (outbound1.z-ptx-11.fr.sopragroup.com [81.80.239.198]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBAFoPib042737 for ; Wed, 10 Dec 2003 07:50:26 -0800 (PST) (envelope-from aalberti@axway.com) Received: by outbound1.sopragroup.com (8.12.10/8.12.10/outbound-A02) with ESMTP id hBAFoHIT009052; Wed, 10 Dec 2003 16:50:18 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: WG LAST CALL: draft-ietf-smime-pss-02.txt Date: Wed, 10 Dec 2003 16:50:17 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG LAST CALL: draft-ietf-smime-pss-02.txt Thread-Index: AcO/L8V5aYrWNXseRkupaoZnffdA0gAAercQ From: "Alberti Antoine" To: "Kaliski, Burt" , "Blake Ramsdell" Cc: X-OriginalArrivalTime: 10 Dec 2003 15:52:24.0406 (UTC) FILETIME=[9A93DF60:01C3BF35] X-Scanned-By: MIMEDefang 2.38 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id hBAFoRib042745 Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I totally agree with Burt's proposition. It tends to mix up a little bit more the concepts of signature and digest (I consider the second one as part of the first one). It also tends to specify, by constraining, more, which is the goal of a specification, from my point of view. Anyway I'd like to make a few comments on this message that are of a very secondary importance. I'm sure some of them will lead to discussions I'd like to see. Moreover, they may point out some of my misunderstandings of the RFCs, in which case it would certainly be of interest for me that somebody explains these to me. > > The draft looks good except for one paragraph: > > The same one-way hash function SHOULD be used for computing the > message digest on the signedAttributes and as the hashAlgorithm in > the RSA-PSS-params structure. > > I think the paragraph should say "MUST". One have to be aware of the fact that SMIME's RFC does not say MUST. > > The id-RSASSA-PSS OID is for the full process of signing a message, > including hashing, padding, and the RSA primitive. > > The RSASSA-PSS-params structure specifies the hash function > that is employed > during hashing and padding. The same hash function is employed in both > steps. So, the hash function in the RSASSA-PSS-params > structure MUST be the > same as the message digest algorithm applied to the > signedAttributes values. This MUST is not a logical consequence of the previous sentences: the 2 digests (the one of the signedAttribute and the one of the signature) are not the same at all. Two distinct digest contexts have to be maintained anyway. > > (If the signedAttributes are omitted, and the eContent value is signed > directly, then the message digest algorithm that is applied > to the eContent > value likewise MUST be the same as the hash function in the > RSASSA-PSS-params structure. I'm not sure if the > eContent-only mode is still > supported in CMS, though.) In this case, it is true that the digest algorithms MUST be the same, as the digests ARE the same one. Furthermore, even if CMS still allows eContent-only signedDatas, SMIME requires the presence of some signedAttributes (contentType, messageDigest, ...) > > id-RSASSA-PSS-params is similar to id-dsa-with-sha1 in that > it specifies the > full process of signing a message. It is different than > rsaEncryption, whcih > only includes padding and the RSA primitive, not hashing. > This is why it > constrains the message digest algorithm, while rsaEncryption doesn't. I still believe that rsaEncryption is an encryption OID, not a signature one. This should logically not (MUST NOT?) be stated as a signature descriptor. Signature OIDs should be sha1WithRSAEncryption, or md5WithRSAEncryption, in this case. Best regards. Antoine Alberti. Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBAExIib040142 for ; Wed, 10 Dec 2003 06:59:18 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBAExIod040141 for ietf-smime-bks; Wed, 10 Dec 2003 06:59:18 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from vulcan.rsasecurity.com (vulcan.rsasecurity.com [204.167.114.130]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBAExHib040128 for ; Wed, 10 Dec 2003 06:59:17 -0800 (PST) (envelope-from BKaliski@rsasecurity.com) Received: from ebola.securitydynamics.com by vulcan.rsasecurity.com via smtpd (for mail.imc.org [208.184.76.43]) with ESMTP; Wed, 10 Dec 2003 09:59:18 -0500 Received: from sdtihq24.securid.com (localhost [127.0.0.1]) by ebola.securitydynamics.com (8.12.10/NULL) with ESMTP id hBAEx61i008505; Wed, 10 Dec 2003 09:59:06 -0500 (EST) Received: from exna00.securitydynamics.com (exna00.securitydynamics.com [10.100.8.217]) by sdtihq24.securid.com (8.12.10/8.12.9) with ESMTP id hBAExAsj024581; Wed, 10 Dec 2003 09:59:12 -0500 (EST) Received: by exna00.securitydynamics.com with Internet Mail Service (5.5.2657.72) id ; Wed, 10 Dec 2003 09:58:56 -0500 Message-ID: From: "Kaliski, Burt" To: "'Blake Ramsdell'" Cc: ietf-smime@imc.org Subject: RE: WG LAST CALL: draft-ietf-smime-pss-02.txt Date: Wed, 10 Dec 2003 09:58:25 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Dear Blake, The draft looks good except for one paragraph: The same one-way hash function SHOULD be used for computing the message digest on the signedAttributes and as the hashAlgorithm in the RSA-PSS-params structure. I think the paragraph should say "MUST". The id-RSASSA-PSS OID is for the full process of signing a message, including hashing, padding, and the RSA primitive. The RSASSA-PSS-params structure specifies the hash function that is employed during hashing and padding. The same hash function is employed in both steps. So, the hash function in the RSASSA-PSS-params structure MUST be the same as the message digest algorithm applied to the signedAttributes values. (If the signedAttributes are omitted, and the eContent value is signed directly, then the message digest algorithm that is applied to the eContent value likewise MUST be the same as the hash function in the RSASSA-PSS-params structure. I'm not sure if the eContent-only mode is still supported in CMS, though.) id-RSASSA-PSS-params is similar to id-dsa-with-sha1 in that it specifies the full process of signing a message. It is different than rsaEncryption, whcih only includes padding and the RSA primitive, not hashing. This is why it constrains the message digest algorithm, while rsaEncryption doesn't. (Note that the padding step also involves a mask generation function, which may be based on a hash function. The above discussion doesn't apply to that hash function; it may or may not be the same as the hash function applied to the message.) -- Burt -----Original Message----- From: Blake Ramsdell [mailto:blake@brutesquadlabs.com] Sent: Wednesday, December 03, 2003 5:54 PM To: ietf-smime@imc.org Subject: WG LAST CALL: draft-ietf-smime-pss-02.txt This message initiates an SMIME Working Group Last Call on the document: Title : Use of the PSS Signature Algorithm in CMS Author(s) : J. Schaad Filename : draft-ietf-smime-pss-02.txt Pages : 5 Date : 2003-12-2 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-02.txt The purpose of this WG Last Call is to ensure that the Working Group has achieved consensus that the document is suitable for publication as a Proposed Standard. Please review the document for both technical and editorial problems. Technical issues should be discussed on this list. Editorial issues may be sent to the document editor. The Last Call period will end on Wednesday, December 10, 2003. Upon completion of the last call, the WG chairs will take action based upon the consensus of the WG. Possible actions include: 1) recommending to the IETF Security Area Directors that the document, after possible editorial or other minor changes, be considered by the IESG for publication as a Standard Track RFC (which generally involves an IETF-wide Last Call); or 2) requiring that outstanding issues be adequately addressed prior to further action (including, possibly, another WG Last Call). Remember that it is our responsibility as Working Group members to ensure the quality of our documents and of the Internet Standards process. So, please read and comment! Blake -- Blake Ramsdell | Brute Squad Labs | http://www.brutesquadlabs.com Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB84Kbib069073 for ; Sun, 7 Dec 2003 20:20:37 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hB84KbP8069072 for ietf-smime-bks; Sun, 7 Dec 2003 20:20:37 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from woodstock.binhost.com (woodstock.binhost.com [144.202.240.3]) by above.proper.com (8.12.10/8.12.8) with SMTP id hB84Kaib069067 for ; Sun, 7 Dec 2003 20:20:36 -0800 (PST) (envelope-from housley@vigilsec.com) Received: (qmail 17213 invoked by uid 0); 8 Dec 2003 04:20:14 -0000 Received: from unknown (HELO Russ-Laptop.vigilsec.com) (12.104.90.162) by woodstock.binhost.com with SMTP; 8 Dec 2003 04:20:14 -0000 Message-Id: <5.2.0.9.2.20031207123029.03e35d50@mail.binhost.com> X-Sender: housley@mail.binhost.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sun, 07 Dec 2003 12:32:42 -0500 To: ietf-smime@imc.org From: Russ Housley Subject: Re: WG LAST CALL: draft-ietf-smime-pss-02.txt In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: An informative note would be helpful. I think the reader would like to know that [RSA-ALGS] includes an ASN.1 module that includes all of the OIDs and structures discussed in this document. Russ At 02:54 PM 12/3/2003 -0800, Blake Ramsdell wrote: >This message initiates an SMIME Working Group Last Call on the document: > > Title : Use of the PSS Signature Algorithm in CMS > Author(s) : J. Schaad > Filename : draft-ietf-smime-pss-02.txt > Pages : 5 > Date : 2003-12-2 > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-02.txt > >The purpose of this WG Last Call is to ensure that the Working Group has >achieved consensus that the document is suitable for publication as a >Proposed Standard. > >Please review the document for both technical and editorial problems. >Technical issues should be discussed on this list. Editorial issues may >be sent to the document editor. > >The Last Call period will end on Wednesday, December 10, 2003. > >Upon completion of the last call, the WG chairs will take action based >upon the consensus of the WG. Possible actions include: > > 1) recommending to the IETF Security Area Directors > that the document, after possible editorial or > other minor changes, be considered by the IESG > for publication as a Standard Track RFC > (which generally involves an IETF-wide Last Call); or > > 2) requiring that outstanding issues be adequately > addressed prior to further action (including, > possibly, another WG Last Call). > >Remember that it is our responsibility as Working Group members to >ensure the quality of our documents and of the Internet Standards >process. So, please read and comment! > >Blake Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB3Ms7ib086942 for ; Wed, 3 Dec 2003 14:54:07 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hB3Ms7Rl086941 for ietf-smime-bks; Wed, 3 Dec 2003 14:54:07 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from brutesquadlabs.com (gtec136-m.isomedia.com [207.115.67.136] (may be forged)) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB3Ms6ib086935 for ; Wed, 3 Dec 2003 14:54:07 -0800 (PST) (envelope-from blake@brutesquadlabs.com) Received: from DEXTER ([192.168.0.6]) by brutesquadlabs.com with ESMTP ; Wed, 3 Dec 2003 14:54:03 -0800 From: "Blake Ramsdell" To: Subject: WG LAST CALL: draft-ietf-smime-pss-02.txt Date: Wed, 3 Dec 2003 14:54:03 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This message initiates an SMIME Working Group Last Call on the document: Title : Use of the PSS Signature Algorithm in CMS Author(s) : J. Schaad Filename : draft-ietf-smime-pss-02.txt Pages : 5 Date : 2003-12-2 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-02.txt The purpose of this WG Last Call is to ensure that the Working Group has achieved consensus that the document is suitable for publication as a Proposed Standard. Please review the document for both technical and editorial problems. Technical issues should be discussed on this list. Editorial issues may be sent to the document editor. The Last Call period will end on Wednesday, December 10, 2003. Upon completion of the last call, the WG chairs will take action based upon the consensus of the WG. Possible actions include: 1) recommending to the IETF Security Area Directors that the document, after possible editorial or other minor changes, be considered by the IESG for publication as a Standard Track RFC (which generally involves an IETF-wide Last Call); or 2) requiring that outstanding issues be adequately addressed prior to further action (including, possibly, another WG Last Call). Remember that it is our responsibility as Working Group members to ensure the quality of our documents and of the Internet Standards process. So, please read and comment! Blake -- Blake Ramsdell | Brute Squad Labs | http://www.brutesquadlabs.com Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB2KbOib045212 for ; Tue, 2 Dec 2003 12:37:24 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hB2KbOuh045209 for ietf-smime-bks; Tue, 2 Dec 2003 12:37:24 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hB2KbMib045196 for ; Tue, 2 Dec 2003 12:37:22 -0800 (PST) (envelope-from dinaras@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08932; Tue, 2 Dec 2003 15:36:35 -0500 (EST) Message-Id: <200312022036.PAA08932@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-smime@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-smime-pss-02.txt Date: Tue, 02 Dec 2003 15:36:35 -0500 Sender: owner-ietf-smime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the S/MIME Mail Security Working Group of the IETF. Title : Use of the PSS Signature Algorithm in CMS Author(s) : J. Schaad Filename : draft-ietf-smime-pss-02.txt Pages : 5 Date : 2003-12-2 This document specifies the conventions for using the RSA Probabilistic Signature Scheme (RSASSA-PSS) digital signature algorithm [P1v2.1] with the Cryptographic Message Syntax (CMS) [CMS]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-smime-pss-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-smime-pss-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-smime-pss-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-12-2154649.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-smime-pss-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-smime-pss-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-12-2154649.I-D@ietf.org> --OtherAccess-- --NextPart--