
From nei.silva@vivax.com.br  Fri Oct 30 20:41:13 2009
Return-Path: <nei.silva@vivax.com.br>
X-Original-To: smime@core3.amsl.com
Delivered-To: smime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C8633A67F5 for <smime@core3.amsl.com>; Fri, 30 Oct 2009 20:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.446
X-Spam-Level: 
X-Spam-Status: No, score=-0.446 tagged_above=-999 required=5 tests=[BAYES_95=3, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 BOJA8pztY8IF for <smime@core3.amsl.com>; Fri, 30 Oct 2009 20:41: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 EF5A63A67C0 for <smime@ietf.org>; Fri, 30 Oct 2009 20:41:11 -0700 (PDT)
Received: from mta0am02.vivax.com.br (mta0am02.vivax.com.br [200.246.46.178]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n9V3fRWg061670 for <ietf-smime@imc.org>; Fri, 30 Oct 2009 20:41:28 -0700 (MST) (envelope-from nei.silva@vivax.com.br)
Received: from neibala (unknown [187.3.170.199]) by mta0am02.vivax.com.br (Postfix) with ESMTP id 4959D478038; Sat, 31 Oct 2009 01:41:14 -0200 (BRST)
Message-ID: <ABA882D663384A02AE44ED8912CD594C@neibala>
From: "Claudinei \(Nei\) - Net - Vivax" <nei.silva@vivax.com.br>
To: <"Undisclosed-Recipient:;"@core3.amsl.com>
Date: Sat, 31 Oct 2009 01:40:11 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01CA59CB.15BCAC40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Antivirus: avast! (VPS 091030-0, 30/10/2009), Outbound message
X-Antivirus-Status: Clean
X-vivax.com.br-MailScanner-Information: Please contact the ISP for more information
X-vivax.com.br-MailScanner: Found to be clean
X-vivax.com.br-MailScanner-SpamScore: sss
X-vivax.com.br-MailScanner-From: nei.silva@vivax.com.br
X-Mailman-Approved-At: Sun, 01 Nov 2009 08:11:59 -0800
Subject: [smime] Fw: Encryption
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2009 11:14:10 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0026_01CA59CB.15BCAC40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

 Encryption=20

       Have you moved or know where to find the DLL to work with encryption=
 format DES (Data Encryption Standard), the intention was to work with vb.n=
et, more if you are in another language I try to do the conversion.=20

Format HSM (Host Security Module), where the customer uses the FK from Form=
 Key Components.=20

With the following formats after=20

Key Length =3D 1 Single length=20
Key Type =3D 001=20
Key Scheme Z =3D Single Length key encrypted using Ansi x9.17 methods=20
Key Component Type =3D X XOR Clear=20
Key Number of Components 3=20


See example=20
password: 5537 is encrypted 57DB18B4AFDE4855 (16 characters) where the key =
was used C44CEF2502C475E5 (where he went to the check value as 90B34B).=20
=20

--=20
Esta mensagem foi verificada pelo sistema de antiv=EDrus e
 acredita-se estar livre de perigo.


------=_NextPart_000_0026_01CA59CB.15BCAC40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =3D=
=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =3D=20
"urn:schemas-microsoft-com:office:odc" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =3D=20
"http://microsoft.com/officenet/conferencing" XMLNS:D =3D "DAV:" XMLNS:Repl=
 =3D=20
"http://schemas.microsoft.com/repl/" xmlns:mt =3D=20
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =3D=20
"http://www.passport.com/NameSpace.xsd" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sub =3D=20
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =3D=
=20
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =3D=20
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =3D=20
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =3D=20
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =3D=20
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =3D=20
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =3D=20
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mv=
er =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =3D=
=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
=3D=20
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =3D=
=20
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
=3D=20
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =3D=
=20
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksServ=
ice"=20
XMLNS:Z =3D "urn:schemas-microsoft-com:" xmlns:st =3D "=01"><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18828">
<STYLE>@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Verdana;
}
@page Section1 {size: 612.0pt 792.0pt; margin: 70.85pt 3.0cm 70.85pt 3.0cm;=
 }
P.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoAcetate {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Texto de bal=E3o Char"
}
LI.MsoAcetate {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Texto de bal=E3o Char"
}
DIV.MsoAcetate {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Texto de bal=E3o Char"
}
SPAN.TextodebaloChar {
	FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link=
: "Texto de bal=E3o"; mso-style-name: "Texto de bal=E3o Char"
}
SPAN.EstiloDeEmail19 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: pe=
rsonal
}
SPAN.EstiloDeEmail20 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: perso=
nal
}
SPAN.EstiloDeEmail21 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DPT-BR link=3Dblue bgColor=3D#ffffff vLink=3Dpurple>
<DIV><o:p>&nbsp;</o:p><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: 12pt"=20
lang=3DEN-US>Encryption <BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Have y=
ou=20
moved or know where to find the DLL to work with encryption format DES (Dat=
a=20
Encryption Standard), the intention was to work with vb.net, more if you ar=
e in=20
another language I try to do the conversion. <BR><BR>Format HSM (Host Secur=
ity=20
Module), where the customer uses the FK from Form Key Components. <BR><BR>W=
ith=20
the following formats after <BR><BR>Key Length =3D 1 Single length <BR>Key =
Type =3D=20
001 <BR>Key Scheme Z =3D Single Length key encrypted using Ansi x9.17 metho=
ds=20
<BR>Key Component Type =3D X XOR Clear <BR>Key Number of Components 3=20
<BR><BR><BR>See example <BR>password: 5537 is encrypted 57DB18B4AFDE4855 (1=
6=20
characters) where the key was used C44CEF2502C475E5 (where he went to the c=
heck=20
value as 90B34B). </SPAN><SPAN style=3D"COLOR: #1f497d"=20
lang=3DEN-US><o:p></o:p></SPAN></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><SPAN=20
lang=3DEN-US><o:p>&nbsp;</o:p></SPAN></P></DIV></BODY><br />--
<br />Esta mensagem foi verificada pelo sistema de antiv=EDrus e=20
<br /> acredita-se estar livre de perigo.
</HTML>

------=_NextPart_000_0026_01CA59CB.15BCAC40--


From wwwrun@core3.amsl.com  Wed Nov 11 10:45:03 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: smime@ietf.org
Delivered-To: smime@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id DD7053A6AEF; Wed, 11 Nov 2009 10:45:03 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20091111184503.DD7053A6AEF@core3.amsl.com>
Date: Wed, 11 Nov 2009 10:45:03 -0800 (PST)
Cc: smime chair <smime-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, smime mailing list <smime@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [smime] Document Action: 'New ASN.1 Modules for CMS and S/MIME' to Informational RFC
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2009 18:45:04 -0000

The IESG has approved the following document:

- 'New ASN.1 Modules for CMS and S/MIME '
   <draft-ietf-smime-new-asn1-07.txt> as an Informational RFC


This document is the product of the S/MIME Mail Security Working Group. 

The IESG contact persons are Tim Polk and Pasi Eronen.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-smime-new-asn1-07.txt

Technical Summary

The Cryptographic Message Syntax (CMS) format, and many associated
formats, are expressed using ASN.1.  The current ASN.1 modules conform to
the 1988 version of ASN.1.  This document updates those ASN.1 modules to
conform to the 2002 version of ASN.1. There are no bits-on-the-wire
changes to any of the formats; this is simply a change to the syntax.

Working Group Summary

This ID was discussed on the SMIME WG mailing list and at IETF 69, 70,
and 71 (SMIME hasn't met since IETF 71).  All SMIME WG Last Call issues
have been resolved.  Discussion during SMIME WG Last Call demonstrated
working group consensus.  This document has SMIME WG support.

Note that the issue raised in PKIX on this document's sister document
draft-ietf-pkix-new-asn1-05.txt (obsolete vs update) was not an issue in
the SMIME WG.  However, it is expected that whatever the result is that
the SMIME WG ID will be on the same track.

Document Quality

This document obsoletes/updates a number of RFCs from the SMIME WG. The
quality of the draft is comparable in quality to its predecessor.

Personnel

Sean Turner is the document Shepherd.  Tim Polk is the responsible
Security Area AD.


From A.Hoenes@TR-Sys.de  Fri Nov 13 08:39:44 2009
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: smime@core3.amsl.com
Delivered-To: smime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 506B63A67F4 for <smime@core3.amsl.com>; Fri, 13 Nov 2009 08:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.079
X-Spam-Level: **
X-Spam-Status: No, score=2.079 tagged_above=-999 required=5 tests=[AWL=0.828,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
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 6IU9S6zfw0Qy for <smime@core3.amsl.com>; Fri, 13 Nov 2009 08:39:43 -0800 (PST)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id CC4323A687C for <smime@ietf.org>; Fri, 13 Nov 2009 08:39:42 -0800 (PST)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA130330359; Fri, 13 Nov 2009 17:39:19 +0100
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id RAA12392; Fri, 13 Nov 2009 17:39:18 +0100 (MEZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <200911131639.RAA12392@TR-Sys.de>
To: turners@ieca.com, smime@ietf.org
Date: Fri, 13 Nov 2009 17:39:17 +0100 (MEZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 8bit
Subject: [smime] draft-turner-asymmetrickeyformat
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2009 16:39:44 -0000

Folks,

RFC 5208 has been published as an Informational RFC with the intent
to transfer change control for PKCS #8 to the IETF and subsequently
bring it to the Standards Track.

draft-turner-asymmetrickeyformat, in the current -02 version
aims at Standards Track and Updating RFC 5208, while keeping
that RFC as a Normative Reference.

That does not seem to be a viable option.


Given that, stripped off boilerplate text, authors' information,
and References, the whole prose text of RFC 5208 amounts to only
roughly four (4) pages, whereas the draft already exceeds that
volume by a factor of two, I strongly suggest to re-write the draft
as a full replacement for RFC 5208, thereby bringing it onto the
Standards Track, as 'promised' by the IESG Note in RFC 5208.


Kind regards,
  Alfred HÎnes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+

