| Re: [eclipse-dev] Notice that Eclipse Platform plans to no longer provide MD5 and SHA1 checksums for Neon (but still SHA512) |
One problem I’ve seen with sha256 is that I couldn’t find a Windows command-line executable to automatically check the checksums.
There’s a couple of UI tools, but for automation a plain command-line sha256.exe (build from GNU coreutils for example) would be good. And no, I wouldn’t want that to be based on Cygwin.
Does anyone have a pointer where to get such a command-line tool, or working instructions how to build myself ?
All I’ve found so far is cross-build instructions here:
https://bugzilla.redhat.com/show_bug.cgi?id=527060#c13
These did work for me but perhaps Eclipse should reference an easier way getting a tool when we switch to sha256 ?
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: <eclipse-dev-bounces@xxxxxxxxxxx>
on behalf of 'David Williams' <david_williams@xxxxxxxxxx>
Reply-To: "eclipse-dev@xxxxxxxxxxx"
<eclipse-dev@xxxxxxxxxxx>
Date: Tuesday 10 May 2016 at 02:37
To: "eclipse-dev@xxxxxxxxxxx"
<eclipse-dev@xxxxxxxxxxx>,
"equinox-dev@xxxxxxxxxxx"
<equinox-dev@xxxxxxxxxxx>,
Cross issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: [eclipse-dev] Notice that Eclipse Platform plans to no longer
provide MD5 and SHA1 checksums for Neon (but still SHA512)
The topic of this note is about the downloads
and checksums obtained directly from the the Eclipse Project. It does not
involve the checksums from the "select a mirror" page -- that
is controlled by the Eclipse Foundation -- nor any of the packages downloaded
from http://www.eclipse.org/downloads--
also controlled by the Eclipse Foundation. My intuition is that few
"casual users" use our checksums but some adopters or committers
might use them in automated scripts or builds.
If any of you do get checksums directly from .../eclipse/downloads/drops4/<buildid>/checksum/...
then this note is for you.
We announced in Luna we would "stop producing MD5 and SHA1 checksums"
after Luna's release (Bug 423714)...
and I am just now getting around to it. Since it has been a long time since
that announcement, and since we are late in this cycle, I am cross-posting
to 3 lists to be sure those that might be impacted will be notified.
We will continue to provide SHA512 checksums and I recently decided to
also provide SHA256 checksums since SHA256 seems to be popular "in
the industry".
This RC1 effort is documented in Bug 454784.
If the removal of the MD5 and SHA1 checksums would unduly burden anyone,
please say so in that Bug 454784 and
we would be happy to accommodate.
I will soon be updating our wiki on How
to verify a download to contain accurate information
for Neon, but wanted to get this notice out now so if you are negatively
impacted you would have time to say so.
Thank you,
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
--
E-Mail: garydgregory@xxxxxxxxx| ggregory@xxxxxxxxxx
Java
Persistence with Hibernate, Second Edition
JUnit
in Action, Second Edition
Spring
Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev