New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
little-flocker hash mismatch #31388
Comments
Submitted a PR to correct this problem #31390 @jwm you can run the following to command to check the hash
Incase you want this to be installed before my PR is merged, you can utilize the below command to do so.
|
Hey guys, Jonathan seems to have performed a hit and run after being hired by Apple, or they required him to seize supporting and offering Little Flocker. 🤷♂️ |
I had the same request as @Miladiir |
Like levanid says, Little Flocker was acquired. Licences are still honored. Download of the "new" product will probably available soon: https://campaigns.f-secure.com/xfence/ |
Hi guys, does anyone have the latest LittleFlocker-1.6.4.dmg and can share it or host it somewhere please? |
Pinging @miccal in case he has one. |
Also asked on twitter (but that shouldn’t get your hopes up much, that account has less than 150 followers). |
Thanks @vitorgalvao, got it and re-uploaded it: https://thireus.com/LITTLEFLOCKER/LittleFlocker-1.6.4.dmg codesign -dv LittleFlocker-1.6.4.dmg:
codesign --verify --strict --verbose LittleFlocker-1.6.4.dmg:
SHA256: 0d23fdecd16cefdaee09a73f3edb7594f3bd2d3585550818fa90426d49053ae3 |
I did not have the |
Thank you @Thireus! Thoughts on this (from your virustotal.com link):
SHA256 Update March 27 SHA256 Update March 26
|
The cask for Little Flocker fails to install due to a hash mismatch:
Downloading its
.dmg
manually yields the "incorrect" hash, but the.pkg
code signature is correct.Maybe the PR updating Little Flocker to 1.6.4 (#31322) used the wrong hash? I contacted support@littleflocker.com. He declined to provide
.dmg
hashes and advised that the code signature on the package was the best way to verify authenticity.The text was updated successfully, but these errors were encountered: