Skip to content
Browse files

Generate some checksum files with more up-to-date hash functions than

MD5. Shipped (and signed) alongside the existing 'md5sums' file.


git-svn-id: svn://svn.tartarus.org/sgt/putty@9189 cda61777-01e9-0310-a592-d414129be87e
  • Loading branch information...
1 parent e030765 commit 0a080c1e34183e089a14114cd782e8ba9045bf0b simon committed
Showing with 14 additions and 7 deletions.
  1. +8 −3 Buildscr
  2. +6 −4 sign.sh
View
11 Buildscr
@@ -98,9 +98,14 @@ deliver putty/windows/*.map maps-x86/$@
# whatever key they want.
deliver putty/sign.sh $@
-# Building the md5sums file is most easily done in the destination
-# directory.
-in-dest putty do md5sum `\find * -type f -print` > md5sums
+# Create files of cryptographic checksums, which will be signed along
+# with the files they verify. We've provided MD5 checksums for a
+# while, but now MD5 is looking iffy, we're expanding our selection.
+#
+# Creating these files is most easily done in the destination
+# directory, where all the files we're delivering are already in their
+# final relative layout.
+in-dest putty do a=`\find * -type f -print`; md5sum $$a > md5sums && sha1sum $$a > sha1sums && sha256sum $$a > sha256sums && sha512sum $$a > sha512sums
# And construct .htaccess files. One in the top-level directory,
# setting the MIME types for Windows help files and providing an
View
10 sign.sh
@@ -3,9 +3,9 @@
# Generate GPG signatures on a PuTTY release/snapshot directory as
# delivered by Buildscr.
-# Usage: sign.sh <builddir> <keytype>
-# e.g. sign.sh build.out Snapshots
-# or sign.sh 0.60 Releases
+# Usage: sh sign.sh <builddir> <keytype>
+# e.g. sh sign.sh putty Snapshots (probably in the build.out directory)
+# or sh sign.sh 0.60 Releases
set -e
@@ -25,5 +25,7 @@ for t in DSA RSA; do
for i in putty*src.zip putty*.tar.gz x86/*.exe x86/*.zip; do
sign --detach-sign "$i" "$i.$t"
done
- sign --clearsign md5sums md5sums.$t
+ for i in md5sums sha1sums sha256sums sha512sums; do
+ sign --clearsign $i ${i}.$t
+ done
done

0 comments on commit 0a080c1

Please sign in to comment.
Something went wrong with that request. Please try again.