[Bug]: MicrosoftOneDrive sha256 is in base64(?) format about evergreen HOT 7 CLOSED

This works to convert, tested with one of the actual values to confirm:

[System.BitConverter]::ToString([Convert]::FromBase64String($Hash)).Replace('-', '').ToLower()

from evergreen.

Thank GitHub Copilot 😂

from evergreen.

Decoding from base64 doesn't give us much to work with:

$base64String = "4rX5bXdtzujmFu6u12fKCcudIEoMMDNUDpgMIrgM79I="
$bytes = [System.Convert]::FromBase64String($base64String)
[System.Text.Encoding]::UTF8.GetString($bytes)

Returns this:

��mwm�����g�	˝ J
                   03T�
                       "�
                         ��

from evergreen.

Yeah, I added the ? because I don't know if it is base64. I couldn't get anything meaningful out of it either, but it sure looks like Base64.

I guess all I'm trying to do is point out that the sha256 attribute is incorrect. I don't know which end of the process creates the problem. (IMHO, it's probably Microsoft.)

from evergreen.

I think it's base64 too, everything I plug it into says it's base64. I don't understand why we aren't getting anything meaningful out of it.

The value comes straight out of the update feed from MS. Should be the property be removed perhaps?

from evergreen.

Unless we expect MS to care enough to fix the problem, I would say it should be removed. Better to not have a checksum property at all than to claim to have one but it is wrong/invalid.

I suppose there is a middle ground, but it requires some validation: Confirm that what the feed returns is hexadecimal and 64 characters long. If not, leave the sha256 property blank (or remove it) for that version.

from evergreen.

thanks @DanGough

from evergreen.