[prev in list] [next in list] [prev in thread] [next in thread]
List: ietf-saag
Subject: Re: [saag] Padding in JWT signing
From: "Salz, Rich" <rsalz=40akamai.com () dmarc ! ietf ! org>
Date: 2023-07-26 17:39:03
Message-ID: B5640E48-B42F-45D5-86A5-33C5F629C1FE () akamai ! com
[Download RAW message or body]
[Attachment #2 (text/plain)]
Yes, I muddled the terms; glad you figured out what I meant.
From: Michael Jones <michael_b_jones@hotmail.com>
Date: Wednesday, July 26, 2023 at 10:37 AM
To: Rich Salz <rsalz@akamai.com>, saag <saag@ietf.org>
Subject: RE: Padding in JWT signing
I believe the dominant JWT signing algorithm is "RS256" [RFC 7518], which is \
RSASSA-PKCS1-v1_5 using SHA-256, which is defined at \
https://www.rfc-editor.org/rfc/rfc3447#section-8.2<https://urldefense.com/v3/__https:/ \
www.rfc-editor.org/rfc/rfc3447*section-8.2__;Iw!!GjvTz_vk!VITJ-dik1LFLO9pmQ1ctukxQXYaHBfX3jsGr3SIIawazY4L23mepDt0d7hnrtq3BW5slY9AHpIERrxBZ9GXyOw77$> \
– also known as PKCS #1. "ES256" is also commonly used - ECDSA using P-256 and \
SHA-256.
OAEP and PKCS 1.5 are encryption algorithms – not signing algorithms. If that's \
what you're asking about, RFC 7518 also defines: "RSA1_5" for RSAES-PKCS1-v1_5
"RSA-OAEP" for RSAES OAEP using default parameters
"RSA-OAEP-256" for RSAES OAEP using SHA-256 and MGF1 with SHA-256
I know that the OpenID Connect working group has deprecated the use of PKCS 1.5. I \
believe that "RSA-OAEP-256" is the predominant encryption algorithm used at this \
point.
-- Mike
From: saag <saag-bounces@ietf.org> On Behalf Of Salz, Rich
Sent: Wednesday, July 26, 2023 10:12 AM
To: saag <saag@ietf.org>
Subject: [saag] Padding in JWT signing
Not sure where to ask this, pointers would be appreciated…. I'm forwarding a \
question someone asked me.
What type of padding is most commonly used in signing JWT ? OAEP or PKCS1.5? Was \
there any security analysis done?
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:x="urn:schemas-microsoft-com:office:excel" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Yes, I muddled the terms; glad you figured out what I \
meant.<o:p></o:p></p> <p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span \
style="font-size:12.0pt;color:black;mso-ligatures:none">From: </span></b><span \
style="font-size:12.0pt;color:black;mso-ligatures:none">Michael Jones \
<michael_b_jones@hotmail.com><br> <b>Date: </b>Wednesday, July 26, 2023 at \
10:37 AM<br> <b>To: </b>Rich Salz <rsalz@akamai.com>, saag \
<saag@ietf.org><br> <b>Subject: </b>RE: Padding in JWT \
signing<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span \
style="mso-ligatures:none"><o:p> </o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:.5in">I believe the dominant JWT signing \
algorithm is "RS256" [RFC 7518], which is RSASSA-PKCS1-v1_5 using SHA-256, which is \
defined at <a href="https://urldefense.com/v3/__https:/www.rfc-editor.org/rfc/rfc3447* \
section-8.2__;Iw!!GjvTz_vk!VITJ-dik1LFLO9pmQ1ctukxQXYaHBfX3jsGr3SIIawazY4L23mepDt0d7hnrtq3BW5slY9AHpIERrxBZ9GXyOw77$">
https://www.rfc-editor.org/rfc/rfc3447#section-8.2</a> – also known as PKCS \
#1. "ES256" is also commonly used - ECDSA using P-256 and \
SHA-256.<o:p></o:p></p> <p class="MsoNormal" \
style="margin-left:.5in"><o:p> </o:p></p> <p class="MsoNormal" \
style="margin-left:.5in">OAEP and PKCS 1.5 are encryption algorithms – not signing \
algorithms. If that's what you're asking about, RFC 7518 also \
defines:<o:p></o:p></p> <p class="MsoNormal" \
style="margin-left:.5in"> \
"RSA1_5" for RSAES-PKCS1-v1_5<o:p></o:p></p> <p class="MsoNormal" \
style="margin-left:.5in"> \
"RSA-OAEP" for RSAES OAEP using default parameters<o:p></o:p></p> <p \
class="MsoNormal" style="margin-left:.5in"> \
"RSA-OAEP-256" for RSAES OAEP using SHA-256 and MGF1 with SHA-256<o:p></o:p></p> <p \
class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p> <p class="MsoNormal" \
style="margin-left:.5in">I know that the OpenID Connect working group has deprecated \
the use of PKCS 1.5. I believe that "RSA-OAEP-256" is the predominant \
encryption algorithm used at this point.<o:p></o:p></p> <p class="MsoNormal" \
style="margin-left:.5in"><o:p> </o:p></p> <p class="MsoNormal" \
style="margin-left:.5in"> & \
nbsp; &nb \
sp;   \
; \
-- Mike<o:p></o:p></p> <p class="MsoNormal" \
style="margin-left:.5in"><o:p> </o:p></p> <div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span \
style="mso-ligatures:none">From:</span></b><span style="mso-ligatures:none"> saag \
<saag-bounces@ietf.org> <b>On Behalf Of </b>Salz, Rich<br>
<b>Sent:</b> Wednesday, July 26, 2023 10:12 AM<br>
<b>To:</b> saag <saag@ietf.org><br>
<b>Subject:</b> [saag] Padding in JWT signing<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Not sure where to ask this, pointers \
would be appreciated…. I'm forwarding a question someone asked me.<o:p></o:p></p> \
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p> <p \
class="MsoNormal" style="margin-left:.5in">What type of padding is most commonly used \
in signing JWT ? OAEP or PKCS1.5? Was there any security analysis \
done?<o:p></o:p></p> </div>
</body>
</html>
_______________________________________________
saag mailing list
saag@ietf.org
https://www.ietf.org/mailman/listinfo/saag
--===============5584000172156537451==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic