Hi Sebastian, > I'll be looking into this and I will either provide some answers > and/or ask more questions as soon as I find either of them.
Thanks! If you can't spot an error in the doc, then perhaps you could provide an example that shows signing working? The example would give: - a hexdump of a single SMB2 packet (netmon can give you this) - a hexdump of a 16 byte session key - a hexdump of the resulting 16 byte signature For example, in my attemped implementation of SMB2 signing this would be: SMB2 packet: (a tree connect) [0000] FE 53 4D 42 40 00 00 00 00 00 00 00 03 00 00 00 [EMAIL PROTECTED] ........ [0010] 08 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 ........ ........ [0020] 00 00 00 00 00 00 00 00 05 00 00 1C 00 04 00 00 ........ ........ [0030] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ [0040] 09 00 00 00 48 00 18 00 5C 00 5C 00 76 00 69 00 ....H... \.\.v.i. [0050] 73 00 74 00 61 00 5C 00 74 00 65 00 73 00 74 00 s.t.a.\. t.e.s.t. session key: [0000] 24 75 2B B3 16 2A BC 20 A6 81 59 8A 69 CD A7 8F $u+..*. ..Y.i... computed signature: [0000] C5 A7 CE 54 35 35 04 C8 8A AC 70 3D 75 A2 96 3D ...T55.. ..p=u..= It is common for crypto algorithms to include examples like this. Cheers, Tridge _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
