On Thu, Aug 10, 2006 at 05:12:48PM -0400, DAve wrote: > SpamAssassin sha1 contents (would all be one line) have the signature first, > f7c3edde6e9e2330318c3fc6a8e70af68387eaeb > /home/updatesd/tmp/stage/3.2.0/update.tgzSHA1 > > My sha1 contents (would all be one line) have the signature last, > (/data/data/lastremaining.com/public_html/updates/tls-local/20060810.tar.gz)= > 8918d6852caab9e57f645e0ff8510c3026fdedd2 > > Line 524 in sa-update is the failure I believe. I suspect anyone > creating a channel on FreeBSD may have the same problem.
FWIW, the format sa-update expects is the standard format from sha1sum. Does FreeBSD have a sha1sum that produces the format that you showed? Answering my own question, FreeBSD seems to not have a "sha1sum", but has a "sha1" which has that kind of format, which seems to be the same output as "openssl sha1 file". Of course to be consistent, "openssl ssl < file" produces just the hash. For now, you may want to either do the openssl redirect thing, or use build/sha1sum.pl from the tarball. Both produce the expected format. If you feel like it, open a BZ ticket about this and we can see about changing the spec/code to accept the 40 byte string at either the start or the end of the line, thereby allowing either format to work. -- Randomly Generated Tagline: "... it's inverted with this little bubble thing ..." - Instructor Dean
pgpynVYk6B7Os.pgp
Description: PGP signature
