11-27-2009
In terms of general usage, they all do pretty much the same. they compute a checksum for a file, allow to compare checksums, and can tell whether 2 files are the same or not. The only difference is the algorithm used. To the best of my knowledge, sum and chksum use pretty general algorithms, while md5sum and sha1sum/sha256sum use cryptographically secure algorithms.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
in HPUX: I am copying oracle datafiles from one mountpoint to another
the total size is about 250Gb. I wanted to perform a checksum on the target and make sure the files came overy properly.
Mountpoints:
/s01 to /u01
/s02 to /u02
I tried using "SUM" on these mountpoints but its taking... (1 Reply)
Discussion started by: jigarlakhani
1 Replies
2. Filesystems, Disks and Memory
Hello,
I am performing a checksum on our software we have installed on a unix solaris 2.0 os.
If the checksum generated report is not the same as a 'Gold' report we have on disk. Then our software is deleted, and reinstalled.
The problem I am having is if you run the program again, the... (3 Replies)
Discussion started by: JustinPyfrom
3 Replies
3. SCO
Does anyone know the answer to this?
When I run "sum -r" on a file that I've down loaded from the sco website, the 1st set of numbers differs from the checksum on the download page but the
2nd set matches.
If I try to install the patch, I get errors.
Anyone has an answer? (3 Replies)
Discussion started by: jn5519
3 Replies
4. Shell Programming and Scripting
Hi ALL,
I use solaris OS and SFTP to get/put files from remote server.I use the below command ,
sftp user@host<<EOF
cd "dir"
get --checksum "filename"
EOF
I am getting a strange error as " get --checksum INVALID paramter". It has been working succesfully since last 3 years but all of a... (1 Reply)
Discussion started by: mohanpadamata
1 Replies
5. Shell Programming and Scripting
Hi Guys,
Sometimes, I have a problem with transferred files in ftp session. Thats why I want to produce checksum value in my local server and remote server. But I could not find anyway to produce checksum value of transferred files in remote server.
Do you have any idea?
Thanks,
Emre (3 Replies)
Discussion started by: ce_emre21
3 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
In file transfer with sftp protocol, what is the purpose "checksum" solves? Is this something not getting the file which has already been bought?
Waiting for your response !!! (1 Reply)
Discussion started by: sk84993
1 Replies
7. Solaris
Hello good people,
I came across md5 checksum. Can anyone please explain to me what it does and if possible an example of how to use it?
Thank you very much (1 Reply)
Discussion started by: cjashu
1 Replies
8. IP Networking
Hello
I am communicating with two devices using my computer over UDP protocol. The application is running fine. When I monitored the UDP traffic using Wireshark software, I found that there were too many Checksum errors.
Please find attached the png file showing this error. I am about to... (0 Replies)
Discussion started by: AustinCann
0 Replies
9. Solaris
Hi Guys,
I have about MD5 checksum so many times but I can't figure out how to use it. Can someone please show me how to perform an MD5 checksum?
Thanks a lot guys. (1 Reply)
Discussion started by: cjashu
1 Replies
10. Shell Programming and Scripting
is there a way to get a script to do a checksum on itself?
something like this:
#!/bin/sh
myexpectedsig=$(cksum $0 | awk '{print $1}')
if ; then
exit
else
who
uptime
date
fi
im looking for something that would always represent the running script, which is why im... (6 Replies)
Discussion started by: SkySmart
6 Replies
LEARN ABOUT DEBIAN
freebsd-cksum
CKSUM(1) BSD General Commands Manual CKSUM(1)
NAME
cksum, sum -- display file checksums and block counts
SYNOPSIS
cksum [-o 1 | 2 | 3] [file ...]
sum [file ...]
DESCRIPTION
The cksum utility writes to the standard output three whitespace separated fields for each input file. These fields are a checksum CRC, the
total number of octets in the file and the file name. If no file name is specified, the standard input is used and no file name is written.
The sum utility is identical to the cksum utility, except that it defaults to using historic algorithm 1, as described below. It is provided
for compatibility only.
The options are as follows:
-o Use historic algorithms instead of the (superior) default one.
Algorithm 1 is the algorithm used by historic BSD systems as the sum(1) algorithm and by historic AT&T System V UNIX systems as the
sum(1) algorithm when using the -r option. This is a 16-bit checksum, with a right rotation before each addition; overflow is dis-
carded.
Algorithm 2 is the algorithm used by historic AT&T System V UNIX systems as the default sum(1) algorithm. This is a 32-bit checksum,
and is defined as follows:
s = sum of all bytes;
r = s % 2^16 + (s % 2^32) / 2^16;
cksum = (r % 2^16) + r / 2^16;
Algorithm 3 is what is commonly called the '32bit CRC' algorithm. This is a 32-bit checksum.
Both algorithm 1 and 2 write to the standard output the same fields as the default algorithm except that the size of the file in
bytes is replaced with the size of the file in blocks. For historic reasons, the block size is 1024 for algorithm 1 and 512 for
algorithm 2. Partial blocks are rounded up.
The default CRC used is based on the polynomial used for CRC error checking in the networking standard ISO/IEC 8802-3:1989. The CRC checksum
encoding is defined by the generating polynomial:
G(x) = x^32 + x^26 + x^23 + x^22 + x^16 + x^12 +
x^11 + x^10 + x^8 + x^7 + x^5 + x^4 + x^2 + x + 1
Mathematically, the CRC value corresponding to a given file is defined by the following procedure:
The n bits to be evaluated are considered to be the coefficients of a mod 2 polynomial M(x) of degree n-1. These n bits are the bits
from the file, with the most significant bit being the most significant bit of the first octet of the file and the last bit being the
least significant bit of the last octet, padded with zero bits (if necessary) to achieve an integral number of octets, followed by one
or more octets representing the length of the file as a binary value, least significant octet first. The smallest number of octets
capable of representing this integer are used.
M(x) is multiplied by x^32 (i.e., shifted left 32 bits) and divided by G(x) using mod 2 division, producing a remainder R(x) of degree
<= 31.
The coefficients of R(x) are considered to be a 32-bit sequence.
The bit sequence is complemented and the result is the CRC.
EXIT STATUS
The cksum and sum utilities exit 0 on success, and >0 if an error occurs.
SEE ALSO
md5(1)
The default calculation is identical to that given in pseudo-code in the following ACM article.
Dilip V. Sarwate, "Computation of Cyclic Redundancy Checks Via Table Lookup", Communications of the ACM, August 1988.
STANDARDS
The cksum utility is expected to conform to IEEE Std 1003.2-1992 (``POSIX.2'').
HISTORY
The cksum utility appeared in 4.4BSD.
BSD
April 28, 1995 BSD