Re: [tram] [Technical Errata Reported] RFC8489 (6268)

[RenThraysk <[e-mail]>]

Here is the test vector generated from my code,
https://github.com/renthraysk/stun/blob/master/rfc8489_test.go (rest of
package is still a work in progress)

00 01 00 90     Request type and message length
21 12 a4 42     Magic cookie
78 ad 34 33  }
c6 ad 72 c0  }  Transaction ID
29 da 41 2e  }
00 1e 00 20     USERHASH attribute header
4a 3c f3 8f  }
ef 69 92 bd  }
a9 52 c6 78  }
04 17 da 0f  }  Userhash value (32  bytes)
24 81 94 15  }
56 9e 60 b2  }
05 c4 6e 41  }
40 7f 17 04  }
00 15 00 29     NONCE attribute header
6f 62 4d 61  }
74 4a 6f 73  }
32 41 41 41  }
43 66 2f 2f  }
34 39 39 6b  }  Nonce value and padding (3 bytes)
39 35 34 64  }
36 4f 4c 33  }
34 6f 4c 39  }
46 53 54 76  }
79 36 34 73  }
41 00 00 00  }
00 14 00 0b     REALM attribute header
65 78 61 6d  }
70 6c 65 2e  }  Realm value (11  bytes) and padding (1 byte)
6f 72 67 00  }
00 1d 00 04     PASSWORD-ALGORITHM attribute header
00 02 00 00     PASSWORD-ALGORITHM value, SHA-256 (0x0002), and parameters
length, 0.
00 1c 00 20     MESSAGE-INTEGRITY-SHA256 attribute header
b5 c7 bf 00  }
5b 6c 52 a2  }
1c 51 c5 e8  }
92 f8 19 24  }  HMAC-SHA256 value
13 62 96 cb  }
92 7c 43 14  }
93 09 27 8c  }
c6 51 8e 65  }

Jared

On Wed, Sep 30, 2020 at 9:45 AM Magnus Westerlund <
[e-mail]> wrote:

> On Mon, 2020-09-28 at 07:54 -0700, Marc Petit-Huguenin wrote:
> > On 9/28/20 7:36 AM, Magnus Westerlund wrote:
> > > Hi,
> > >
> > > A question here. Is the key used in the MESSAGE-INTEGRITY-SHA256 the
> MD5
> > > derived
> > > one, or one derived using SHA256? If it is the former, then fine the
> lets
> > > just
> > > add a sentence of clarification as the option exist. But, Jared's
> previous
> > > comments appear to indicate the the key for the HMAC-SHA256 used in the
> > > intergrity was derived using SHA256. If it is the later, then I don't
> see
> > > any
> > > option than to include the password algorithm attribute and its
> algorithm
> > > indicator as it is a necessary component to correctly derive the key
> and
> > > thus
> > > being able to verify the MESSAGE-INTEGRITY.
> >
> > SHA256.
>
> So in this case then the PASSWORD-ALGORITM attribute is required unless I
> missinterpret the RFC. I understand that there is some work in preparing
> the
> message and calculate the integrity. However, in this case it is necessary
> information and a mandated value so can you please prepare a new message
> with
> the attribute include indicating the correct value?
>
>
> Cheers
>
> Magnus Westerlund
>
>
> ----------------------------------------------------------------------
> Networks, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Mobile [phone]
> Torshamnsgatan 23           |
> SE-164 80 Stockholm, Sweden | mailto: [e-mail]
> ----------------------------------------------------------------------
>
>
>