I'm probably missing something obvious but:

Do the following 50 times: Take the output of the previous MD5 call and pass it as input to MD5. Take the output of the final MD5 call. Truncate it down to be the same length as the value specified by key length. This is the symmetric key.

the output from the md5 hash is always 16 bytes so it would never need to be truncated?

Also any chance of a test vectors for the two parts symmetric key and user hash on their own? Cheers

Truncation only applies when the symmetric key is export grade i.e. 40 bits. You indeed don't have to worry about it for this problem. And yes, I'll add a test vector later today.

Can you provide the test vector values for intermediate steps like "padded out" password value and first md5 value please. I tried a bunch of variations but not getting the symmetric key value to match

Sure, a couple things to keep in mind:

• The given document ID and the owner hash are hex encoded, the MD5 algorithm operates on raw bytes so you'll want to decode those before passing them to MD5.
• Permissions is the hex representation (in two's complement) of -3 in this case. Just interpret it as a hex encoded string like the above two values and do the same decoding before feeding it to MD5.

Padded out password (hex encoded):

70617373776f726428bf4e5e4e758a4164004e56fffa01082e2e00b6d0683e80

First MD5 digest (hex encoded):

dc062d97761b94aa0edb28caa44c4e4e