-
Notifications
You must be signed in to change notification settings - Fork 2.1k
0.8.10 not signed, and insecure checksum given in release #2272
Comments
@luclu can you change our build server to generate SHA256 checksums again? |
@evertonfraga with pleasure, I will also update them for the geth bins as the sha256 checking routine has now been included for over 5 releases. |
Weird this hasn't been fixed yet. Nobody should install an unsigned binary, that's a bad habit to get into where valuable data is at stake. Can you please escalate? It would be good to see the signing become well established as part of your build process, and unquestioned. |
What is the status of this issue? Mac OSX version 8.10 has incorrect file name associated with MD5 checksum. Version for download is not named 'unsigned'' and downloaded version is actually signed. |
Lack of response gives me an uncomfortable feeling about Ethereum processes. |
As promised, https://github.com/ethereum/mist/releases/tag/v0.8.10 |
@hwinkler we had a huge amount of issues opened in the last weeks, due to increasing attention drawn to ethereum. That slowed down our ability to cope with the issues, but we're working on this. I am closing this, thanks. |
SHA-256 checksums are back on our build process: #2917 Also, they are listed on v0.9.0 release. Thanks. |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Part of this has already been brought up in #2236, but I don't think the issue was sufficiently addressed.
I have two concerns:
Why the sudden discrepancy in the release process?
The text was updated successfully, but these errors were encountered: