Hi all. Zcash has identified and fixed a critical security flaw. Both Zcash v1.0.8-1 and the just-released ZClassic v1.0.8 have the security patch applied. PLEASE UPDATE YOUR NODE ASAP.
[Moderator Edit] Zcash v1.0.8 is vulnerable, and v1.0.8-1 has the fix. I changed the mistake above for safety to avoid confusion. The v1.0.8-1 version is tagged, but we haven’t built official binaries. We’ll post the official security disclosure once binaries are released. -Nathan
The Zclassic devs requested that I spread the word, and at that time told me Zcash was merging the patch. I looked at the Zcash repo and say a reference to the patch, so I posted the repo link.
Edit: Next time I’ll just address the ZClassic folks, if that’s what you want.
Hi @anon47418038, getting an interesting message after updating the binaries for zcashd to 1.0.8-1 (see screenshot below). I did overwrite the original binaries in /Applications/zcash4mac.app/Contents/Java with the ones in your package. Maybe I shouldn’t have? Anyway’s here’s the screenshot. I’ll try to zap some milliZEC to the wallet to see if it’s actually updating.
I’d go into “Add/Remove Programs” and uninstall zcash4win and download the new release (ugh, same file name, which is a limitation of Windows Installer) from https://zcash4win.com
Anyways, I cashed out some milliZEC from my mining pool and I can see that the transaction shows up successfully. To some extent, the java client can communicate with the zcashd daemon, but it throws these errors and I can’t see my balance. I’ll keep tinkering with it.
oh derp…I didn’t overwrite, that might make things unhappy…I working on updating the GUI with some things and will push a new installer for zcash4mac soon.
In the meantime I’d reinstall zcash4mac, and run the zcashd in the zipfile from Terminal before launching it.
Just as a side note, the method proposed by @anon47418038 (reinstall zcash4mac, kill any running zcashd process and run the process from the zip before launching the client) worked perfectly.