Comment 14 for bug 561800

Revision history for this message
In , Jonny-lamb (jonny-lamb) wrote :

After putting these details on the wrong bug by accident, I'll try again:

Okay, that log was pretty useful and shows what's wrong with the SHA1D. Here is
msn object XML:

<msnobj <email address hidden>" Size="19086" Type="3"
Location="TFRlgrTEF.dat" Friendly="SQBtAGEAZwBlAG4AIAAxADAAAAA=" SHA1D="1h
Jo825av2d/RagyNCPI0V3rTs=" SHA1C="VK4lMv5Ori9LfY1J6THi4o/sOAU="/>

Take the SHA1D attribute:

    SHA1D="1h Jo825av2d/RagyNCPI0V3rTs="

I've no idea what that "1h", but we need to work around it. I had a little look
at the other MSN implementations and couldn't find anything about this. I'll
cook up a patch.

Oh, also, the rogue string isn't always first in the SHA1D attribute:

% grep "Invalid SHA1" butterfly-log.txt
papyon/papyon.p2p-WARNING: 14/04/10 18:16:26.809406: Invalid SHA1D in
MSNObject: /IkRrvJpPvK/ZFEZEM7eRhle k4=
papyon/papyon.p2p-WARNING: 14/04/10 18:16:27.35620: Invalid SHA1D in MSNObject:
1h Jo825av2d/RagyNCPI0V3rTs=
papyon/papyon.p2p-WARNING: 14/04/10 19:18:38.737390: Invalid SHA1D in
MSNObject: 1h Jo825av2d/RagyNCPI0V3rTs=
papyon/papyon.p2p-WARNING: 14/04/10 19:20:31.38971: Invalid SHA1D in MSNObject:
1h Jo825av2d/RagyNCPI0V3rTs=

:-(