Snapins not downloading to client - Hash check error

[sideone]

Hello,

we’ve just upgraded to 1.5.10.37 (although the problem was happening on *.36 too).

Snapins are replicating to storage nodes correctly, but when downloading to a client PC they’re getting a hash error

 19/07/2024 13:29:04 SnapinClient ERROR: Hash does not match
 19/07/2024 13:29:04 SnapinClient ERROR: --> Ideal: *REDACTED for spam filter*
 19/07/2024 13:29:04 SnapinClient ERROR: --> Actual: *REDACTED for spam filter*

A 1kb file is downloaded with the correct filename, but doesn’t open. When renaming the file extension to .txt, the file actually contains:

Please update your FOG Client, this is old and insecure

Are snapins broken on the latest trunk release? Do I need to roll back, or do I need to update the FOG client on all machines?

Cheers!

[Tom Elliott]

@sideone So we’re looking into the issue.

I updated the old “legacy” sender method, but I may have forgotten that the file deploy process depends on the same “old” methodology.

I haven’t confirmed (or rather we (@JJ-Fullmer) for sure yet, but now that this is brought up, it’s one thing I have at the forefront of my brainbox. Thank you!

[sideone]

@Tom-Elliott version .41 has solved the issue. Thank you so much!