@MSGID: 1:320/219@fidonet 66293174
@REPLY: 1:218/910 337ac29f
@CHRS: UTF-8 2
@TZUTC: -0400
@TID: MBSE-FIDO 1.0.8.7 (Linux-x86_64)
Hello Jason!

23 Apr 24 16:11, you wrote to all:

 JB> Question regarding FTS-1027 section 1.7 "Example of Frame Exchange
 JB> During CRAM Authentication"

 JB> In the example, the Originating side returns

 JB>   M_PWD "CRAM-MD5-56be002162a4a15ba7a9064f0c93fd00"

 JB> This hex value appears to be incorrect. I tested with two
 JB> implementations of the CRAM-MD5 algorithm, and in both cases, the same
 JB> hex value was calculated using the password and challenge hex string
 JB> from the example, which differed from the value shown in the document.

 JB> Password:   tanstaaftanstaaf
 JB> Challenge:  f0315b074d728d483d6887d0182fc328
 JB> Expected:   56be002162a4a15ba7a9064f0c93fd00  <- From section 1.7
 JB> example
 JB> Result:     1503922bb6a38bc934bca7afeb522d28  <- From both MD5
 JB> algorithms

 JB> Which is correct - the value shown in section 1.7 or the test result
 JB> value?

I will do some testing and attempt to validate your concern.

Andrew

--- GoldED+/LNX 1.1.5-b20240209
 * Origin: From the Desk of the FTSC Administrator (1:320/219)
SEEN-BY: 1/19 123 16/0 19/37 30/0 50/109 103/705
104/117 106/201 123/130
SEEN-BY: 124/5016 129/215 132/174 142/104 153/757
7001 7715 154/10 30 203/0
SEEN-BY: 221/0 1 6 229/426 240/1120 2100 5411
5824 5832 5853 5890 6309 261/1
SEEN-BY: 275/100 280/464 5003 5006 5555 292/854
8125 301/1 113 310/31 320/119
SEEN-BY: 320/219 319 2119 326/101 335/364 341/66
234 396/45 423/120 460/58
SEEN-BY: 467/888 633/280 509 712/848 770/1 2432/390
2454/119 3634/12 5001/100
SEEN-BY: 5005/49 5020/400 545 846 848 1042 4441
12000 5030/49 1081 1474
SEEN-BY: 5053/51 5054/8 5061/133 5075/128 5083/1
444
@PATH: 320/219 240/5832 280/464 301/1 5020/1042
4441