search

digitalsleuth / WIN-FOR

Windows Forensics Environment Builder
https://digitalsleuth.gitbook.io/win-for-documentation/
MIT License
106 stars 18 forks source link

Hash mismatch errors on 8.30 in Windows 10 and Windows 11 #4

Closed 4NSIK1 closed 1 year ago

4NSIK1 commented 1 year ago

Hi DigitalSleuth, I have been using win-for 8.30 release with success, but today when trying to install it on Win10 or Win11 VirtualBox VM it is having a hash mismatch with the win-for-salt-v2023.26.2.zip - pic attached.
Is there anything I can do to fix this? Thanks Robert SCR-20231003-oks

4NSIK1 commented 1 year ago

I installed Salt 3005.2.1 manually but the SHA256 mismatch appears to be the issue between the calculated hash and the stored hash. SCR-20231004-9up-3

digitalsleuth commented 1 year ago

Hi @4NSIK1 , the issue is actually with the release file and not with Saltstack. I'll be issuing a new release of the Salt States this evening which should fix that issue, and encompass many changes. I'll also release a new version of the Win-FOR Customizer in the next day or two which will add some new features.

I'll let you know as soon as the Salt State issue is fixed!

4NSIK1 commented 1 year ago

Brilliant, @digitalsleuth thanks so much. I am loving this tool.

digitalsleuth commented 1 year ago

Hi @4NSIK1 , I've released a new version, v2023.27.0, which should address this issue, Let me know how it goes.

Cheers!

digitalsleuth commented 1 year ago

Hi @4NSIK1 , well the new version had a few bugs, so I've fixed those and released a new one, v2023.27.1. This should fix all the issues.

Cheers!

digitalsleuth commented 1 year ago

Hi @4NSIK1 I've confirmed that this issue has been resolved. On a side note, I've released a new version of WIN-FOR v8.4.0 which removes the internal dependency of a stored hash for SaltStack and Git and allows for the proper version and hash to be checked from the winfor-salt repo.

Cheers, and thanks for the feedback!

afp235 commented 10 months ago

Hi @digitalsleuth, I know you mentioned this has been resolved but I'm getting this same issue with the newest version:

wfor

Is there anything that I could do to solve this?

digitalsleuth commented 10 months ago

Hi @afp235 , this issue should be resolved now. It appears to be an issue with some changes happening on Github's end. I've re-uploaded the current version (with a new version number), and everything should work now.