Re: New version of PSKC
From: Philip Hoyer [mailto:phoyer-AGozWa3SCxNa+Cujyj6rOQC/G2K4zDHf@public.gmane.org]
Sent: Wednesday, September 02, 2009 5:18 AM
To: Pei, Mingliang; Hannes.Tschofenig-hi6Y0CQ0nG0@public.gmane.org; Phillip Hallam-Baker; Salah Machani; Sean Turner
Cc: Doherty, Andrea; Magnus Nyström; KEYPROV
Subject: RE: New version of PSKC
Ming and all,Please see questions and explanation of my perplexion below. Bear with me.Which MAC key for which example?My main concern are the PBE examples that you generated and the existing one forget for a moment the namsespace change.Following are some differences (highlighted in bold):SPEC ONE:Lets start with an extract of the existing one in the spec:<pskc:MACMethod
Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1">
<pskc:MACKey>
<xenc:EncryptionMethod
Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/>
<xenc:CipherData>
<xenc:CipherValue>
2GTTnLwM3I4e5IO5FkufoNhk05y8DNyOHuSDuRZLn6DhIjoTY/dX4SkUAbQ
SWJblA7Dzi031L6FNnUrcjsGGcQ==
</xenc:CipherValue>
</xenc:CipherData>
</pskc:MACKey>
</pskc:MACMethod>GENERATED ONE:<pskc:MACMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1">
<pskc:MACKey>
<xenc:EncryptionMethod Algorithm="http://www.rsasecurity.com/rsalabs/pkcs/schemas/pkcs-5#pbes2">
<pskc:EncryptionScheme Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/>
</xenc:EncryptionMethod>
<xenc:CipherData>
<xenc:CipherValue>2GTTnLwM3I4e5IO5FkufoOEiOhNj91fhKRQBtBJYluUDsPOLTfUvoU2dStyOwYZx</xenc:CipherValue>
</xenc:CipherData>
</pskc:MACKey>
</pskc:MACMethod>
Now I do not understand why we need EncryptionScheme at all. Should it not be as the one in the spec?I have the same question about EncryptionScheme later in both examples:SPEC ONE:....<pskc:Secret><pskc:EncryptedValue Id="ED">
<xenc:EncryptionMethod
Algorithm=
"http://www.rsasecurity.com/rsalabs/pkcs/schemas/pkcs-5#pbes2">
<pskc:EncryptionScheme
Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/>
</xenc:EncryptionMethod>
<xenc:CipherData>
<xenc:CipherValue>
oTvo+S22nsmS2Z/RtcoF8Hfh+jzMe0RkiafpoDpnoZTjPYZu6V+A4aEn032yCr4f
</xenc:CipherValue>
</xenc:CipherData>
GENERATED ONE:ryptedValue>
<xenc:EncryptionMethod Algorithm="http://www.rsasecurity.com/rsalabs/pkcs/schemas/pkcs-5#pbes2">
<pskc:EncryptionScheme Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/>
</xenc:EncryptionMethod>
<xenc:CipherData>
<xenc:CipherValue>oTvo+S22nsmS2Z/RtcoF8Hfh+jzMe0RkiafpoDpnoZTjPYZu6V+A4aEn032yCr4f</xenc:CipherValue>
</xenc:CipherData>
Why do we need EncryptionScheme at all? Since we know it is a derived key in the main element?Should these not be like the preshared key one?:PRE-SHARED-KEY<Secret>
<EncryptedValue>
<xenc:EncryptionMethod
Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/>
<xenc:CipherData>
<xenc:CipherValue>
AAECAwQFBgcICQoLDA0OD+cIHItlB3Wra1DUpxVvOx2lef1VmNPCMl8jwZqIUqGv
</xenc:CipherValue>
</xenc:CipherData>
</EncryptedValue>
<ValueMAC>aSRlEG1agUo0CS2dt/OvIAqQ6Co=
</ValueMAC>
</Secret>
Also should we align the examples that they use prefixed namespace for pskc. e.g. <pskc:element> I rather have default namespace of pskc so that it reads: <element>.Additional question, should we add the xenc11 import statement to the schema?Philip
From: Pei, Mingliang [mailto:mpei-0nFLJxsdniVWk0Htik3J/w@public.gmane.org]
Sent: Wed 02/09/2009 7.43
To: Philip Hoyer; Hannes.Tschofenig-hi6Y0CQ0nG0@public.gmane.org; Phillip Hallam-Baker; Salah Machani; Sean Turner
Cc: Doherty, Andrea; Magnus Nyström; KEYPROV
Subject: RE: New version of PSKC
Hi Philip,Please see the forwarded email that includes the examples from my implementation that I sent earlier. The latest draft doesn't seem to have the CipherValue for the MAC key right. Please update it to2GTTnLwM3I4e5IO5FkufoOEiOhNj91fhKRQBtBJYluUDsPOLTfUvoU2dStyOwYZxThanks,- MingFrom: Philip Hoyer [mailto:phoyer-AGozWa3SCxNa+Cujyj6rOQC/G2K4zDHf@public.gmane.org]
Sent: Friday, August 28, 2009 9:56 AM
To: Hannes.Tschofenig-hi6Y0CQ0nG0@public.gmane.org; Phillip Hallam-Baker; Pei, Mingliang; Salah Machani; Sean Turner
Cc: Doherty, Andrea; Magnus Nyström; KEYPROV
Subject: New version of PSKC
Ladies and Gentlemen,
Please find attached the new version of PSKC.
Changes:
- incorporated all of the feedback from Andrea and Sean.
- reference name change to the new DerivedKey element (moved to XMLEnc11)
- Corrected AES example to include (prepend) IV inline with XMLENC spec and mentions IV handling.
I have one big problem:
The samples that Ming sent out for PBE and RSA do not match the ones in the spec.
Especially the PBE is different form the one Ming already says was corrected.
Based on the new XML Enc 1.1 spec for PBE and DerivedKeys. Are we sure we are aligned here?
This is the only thing that needs to be clarified.
Otherwise,
What do I need to do now.
Do I just submit or send to Russ and Pasi directly?
Philip
________________________________
Philip Hoyer
Senior Architect - Office of CTO
ActivIdentity (UK)
117 Waterloo Road
London SE1 8UL
Telephone: +44 (0) 20 7960 0220
Fax: +44 (0) 20 7902 1985
Private and confidential: This message and any attachments may contain
privileged / confidential information. If you are not an intended recipient,
you must not copy, distribute, discuss or take any action in reliance on it.
If you have received this communication in error, please notify the sender
and delete this message immediately.
<div> <div dir="ltr" align="left"><span class="048384019-02092009">The reason is that DerivedKey portion only describe how a key is derived for a desired length, not indicating how a key is used. For PBES2, the encryption scheme parameter is required. It should either go to PKCS#5 parameters, or EncryptionMethod part of the xenc:EncryptedDataType. We chose the second one. The encrytion key element contains only the key portion as we have been doing, similar to the pre-shared key case. It is consistent. The common element EncryptionKey includes the key data information, not the encryption algorithm information.</span></div> <div dir="ltr" align="left"> <span class="048384019-02092009"></span> </div> <div dir="ltr" align="left"><span class="048384019-02092009">- Ming</span></div> <br><blockquote dir="ltr"> <div class="OutlookMessageHeader" lang="en-us" dir="ltr" align="left"> From: Philip Hoyer [mailto:phoyer@...] <br>Sent: Wednesday, September 02, 2009 5:18 AM<br>To: Pei, Mingliang; Hannes.Tschofenig@...; Phillip Hallam-Baker; Salah Machani; Sean Turner<br>Cc: Doherty, Andrea; Magnus Nyström; KEYPROV<br>Subject: RE: New version of PSKC<br><br> </div> <div></div> <div dir="ltr"> <div dir="ltr">Ming and all,</div> <div dir="ltr"> </div> <div dir="ltr">Please see questions and explanation of my perplexion below. Bear with me.</div> <div dir="ltr"> </div> <div dir="ltr">Which MAC key for which example?</div> <div dir="ltr"> </div> <div dir="ltr">My main concern are the PBE examples that you generated and the existing one forget for a moment the namsespace change.</div> <div dir="ltr"> </div> <div dir="ltr">Following are some differences (highlighted in bold):</div> <div dir="ltr"> </div> <div dir="ltr">SPEC ONE:</div> <div dir="ltr">Lets start with an extract of the existing one in the spec:</div> <div dir="ltr"> </div> <div dir="ltr"> <pskc:MACMethod <br> Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"><br> <pskc:MACKey><br> <xenc:EncryptionMethod <br> Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/><br> <xenc:CipherData><br> <xenc:CipherValue><br>2GTTnLwM3I4e5IO5FkufoNhk05y8DNyOHuSDuRZLn6DhIjoTY/dX4SkUAbQ<br>SWJblA7Dzi031L6FNnUrcjsGGcQ==<br> </xenc:CipherValue><br> </xenc:CipherData><br> </pskc:MACKey><br> </pskc:MACMethod></div> <div dir="ltr"> </div> <div dir="ltr">GENERATED ONE:</div> <div dir="ltr"> </div> <p dir="ltr"><pskc:MACMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"></p> <p dir="ltr"><pskc:MACKey></p> <p dir="ltr"><xenc:EncryptionMethod Algorithm="http://www.rsasecurity.com/rsalabs/pkcs/schemas/pkcs-5#pbes2"></p> <p dir="ltr"><pskc:EncryptionScheme Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/></p> <p dir="ltr"></xenc:EncryptionMethod></p> <p dir="ltr"><xenc:CipherData></p> <p dir="ltr"><xenc:CipherValue>2GTTnLwM3I4e5IO5FkufoOEiOhNj91fhKRQBtBJYluUDsPOLTfUvoU2dStyOwYZx</xenc:CipherValue></p> <p dir="ltr"></xenc:CipherData></p> <p dir="ltr"></pskc:MACKey></p> <p dir="ltr"></pskc:MACMethod></p> </div> <div dir="ltr"> </div> <div dir="ltr">Now I do not understand why we need EncryptionScheme at all. Should it not be as the one in the spec?</div> <div dir="ltr"> </div> <div dir="ltr"> </div> <div dir="ltr">I have the same question about EncryptionScheme later in both examples:</div> <div dir="ltr"> </div> <div dir="ltr"> </div> <div dir="ltr">SPEC ONE:</div> <div dir="ltr"> </div> <div dir="ltr">....</div> <div dir="ltr"><pskc:Secret></div> <div dir="ltr"> <div dir="ltr"> <pskc:EncryptedValue Id="ED"><br> <xenc:EncryptionMethod <br> Algorithm=<br>"http://www.rsasecurity.com/rsalabs/pkcs/schemas/pkcs-5#pbes2"><br> <pskc:EncryptionScheme<br>Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/><br> </xenc:EncryptionMethod><br> <xenc:CipherData><br> <xenc:CipherValue><br> oTvo+S22nsmS2Z/RtcoF8Hfh+jzMe0RkiafpoDpnoZTjPYZu6V+A4aEn032yCr4f<br> </xenc:CipherValue><br> </xenc:CipherData><br> </div> <div dir="ltr">GENERATED ONE:</div> <div dir="ltr"> <p>ryptedValue></p> <p><xenc:EncryptionMethod Algorithm="http://www.rsasecurity.com/rsalabs/pkcs/schemas/pkcs-5#pbes2"></p> <p><pskc:EncryptionScheme Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/></p> <p></xenc:EncryptionMethod></p> <p><xenc:CipherData></p> <p><xenc:CipherValue>oTvo+S22nsmS2Z/RtcoF8Hfh+jzMe0RkiafpoDpnoZTjPYZu6V+A4aEn032yCr4f</xenc:CipherValue></p> <p></xenc:CipherData></p> </div> <div dir="ltr"> </div> <div dir="ltr"> <div dir="ltr">Why do we need EncryptionScheme at all? Since we know it is a derived key in the main element?</div> <div dir="ltr"> </div> <div dir="ltr">Should these not be like the preshared key one?:</div> <div dir="ltr"> </div> <div dir="ltr">PRE-SHARED-KEY</div> <div dir="ltr"> </div> <div dir="ltr"><Secret><br> <EncryptedValue><br> <xenc:EncryptionMethod <br> Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/><br> <xenc:CipherData><br> <xenc:CipherValue><br> AAECAwQFBgcICQoLDA0OD+cIHItlB3Wra1DUpxVvOx2lef1VmNPCMl8jwZqIUqGv<br> </xenc:CipherValue><br> </xenc:CipherData><br> </EncryptedValue><br> <ValueMAC>aSRlEG1agUo0CS2dt/OvIAqQ6Co= <br> </ValueMAC><br> </Secret><br> </div> </div> <div dir="ltr"> </div> <div dir="ltr">Also should we align the examples that they use prefixed namespace for pskc. e.g. <pskc:element> I rather have default namespace of pskc so that it reads: <element>.</div> <div dir="ltr"> </div> <div dir="ltr">Additional question, should we add the xenc11 import statement to the schema?</div> <div dir="ltr"> </div> <div dir="ltr">Philip</div> <div dir="ltr"> </div> </div> <div dir="ltr"> <br>From: Pei, Mingliang [mailto:mpei@...]<br>Sent: Wed 02/09/2009 7.43<br>To: Philip Hoyer; Hannes.Tschofenig@...; Phillip Hallam-Baker; Salah Machani; Sean Turner<br>Cc: Doherty, Andrea; Magnus Nyström; KEYPROV<br>Subject: RE: New version of PSKC<br><br> </div> <div> <div dir="ltr" align="left"><span class="790313805-02092009">Hi Philip,</span></div> <div dir="ltr" align="left"> <span class="790313805-02092009"></span> </div> <div dir="ltr" align="left"><span class="790313805-02092009">Please see the forwarded email that includes the examples from my implementation that I sent earlier. The latest draft doesn't seem to have the CipherValue for the MAC key right. Please update it to</span></div> <div dir="ltr" align="left"> <span class="790313805-02092009"></span> </div> <div dir="ltr" align="left"><span class="790313805-02092009">2GTTnLwM3I4e5IO5FkufoOEiOhNj91fhKRQBtBJYluUDsPOLTfUvoU2dStyOwYZx</span></div> <div dir="ltr" align="left"> <span class="790313805-02092009"></span> </div> <div dir="ltr" align="left"><span class="790313805-02092009">Thanks,</span></div> <div dir="ltr" align="left"> <span class="790313805-02092009"></span> </div> <div dir="ltr" align="left"><span class="790313805-02092009">- Ming</span></div> <br><blockquote dir="ltr"> <div class="OutlookMessageHeader" lang="en-us" dir="ltr" align="left"> From: Philip Hoyer [mailto:phoyer@...] <br>Sent: Friday, August 28, 2009 9:56 AM<br>To: Hannes.Tschofenig@...; Phillip Hallam-Baker; Pei, Mingliang; Salah Machani; Sean Turner<br>Cc: Doherty, Andrea; Magnus Nyström; KEYPROV<br>Subject: New version of PSKC<br><br> </div> <div></div> <div class="Section1"> <p class="MsoNormal"><span lang="EN-GB">Ladies and Gentlemen,</span></p> <p class="MsoNormal"><span lang="EN-GB">Please find attached the new version of PSKC.</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Changes:</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <ul type="disc"> <li class="MsoNormal"> <span lang="EN-GB">incorporated all of the feedback from Andrea and Sean.</span> </li> <li class="MsoNormal"> <span lang="EN-GB">reference name change to the new DerivedKey element (moved to XMLEnc11)</span> </li> <li class="MsoNormal"> <span lang="EN-GB">Corrected AES example to include (prepend) IV inline with XMLENC spec and mentions IV handling.</span> </li> </ul> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">I have one big problem:</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">The samples that Ming sent out for PBE and RSA do not match the ones in the spec.</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Especially the PBE is different form the one Ming already says was corrected.</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Based on the new XML Enc 1.1 spec for PBE and DerivedKeys. Are we sure we are aligned here?</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">This is the only thing that needs to be clarified.</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Otherwise,</span></p> <p class="MsoNormal"><span lang="EN-GB">What do I need to do now.</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Do I just submit or send to Russ and Pasi directly?</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Philip</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">________________________________</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Philip Hoyer </span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Senior Architect - Office of CTO</span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">ActivIdentity (UK)</span></p> <p class="MsoNormal"><span lang="EN-GB">117 Waterloo Road</span><span lang="EN-GB"></span></p> <p class="MsoNormal"><span lang="EN-GB">London</span><span lang="EN-GB"> SE1 8UL</span><span lang="EN-GB"></span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Telephone: +44 (0) 20 7960 0220</span><span lang="EN-GB"></span></p> <p class="MsoNormal"><span lang="EN-GB">Fax: +44 (0) 20 7902 1985</span><span lang="EN-GB"></span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> <p class="MsoNormal"><span lang="EN-GB">Private and confidential: This message and any attachments may contain</span></p> <p class="MsoNormal"><span lang="EN-GB">privileged / confidential information. If you are not an intended recipient,</span></p> <p class="MsoNormal"><span lang="EN-GB">you must not copy, distribute, discuss or take any action in reliance on it.</span></p> <p class="MsoNormal"><span lang="EN-GB">If you have received this communication in error, please notify the sender</span></p> <p class="MsoNormal"><span lang="EN-GB">and delete this message immediately.</span><span lang="EN-GB"></span></p> <p class="MsoNormal"><span lang="EN-GB"></span> </p> </div> </blockquote> </div> </blockquote> </div>
RSS Feed