Sponsored Content
Full Discussion: Hashsums and collisions
Special Forums Cybersecurity Hashsums and collisions Post 302966284 by jim mcnamara on Wednesday 10th of February 2016 11:17:30 AM
Old 02-10-2016
Look up the concept of 'avalanche'

Choosing a Good Hash Function, Part 3

and for example the jenkins hashes:

https://en.wikipedia.org/wiki/Jenkins_hash_function
 

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solving the network collisions in Unix box

Hi, Anyone can u give me an idea to clear the network collisions in the unix box(Solaris and Linux)? NIC performance is very low, and it shows collisions, when issuing the command ifconfig -a in the production server. How can i rectify the network collisions in the box. Using netstat and lsof... (4 Replies)
Discussion started by: muthulingaraja
4 Replies

2. IP Networking

Acceptable collisions

Hi All I have a Sun V120 with eri0 NIC set to 10-Half connected to Fa0/0 on a Cisco 2600 (Fa0/0 also set to 10-Half). I am seeing collisions on this link (as expectd with a 10-Half connection) BUT, what is an acceptable rate of collisions for this type of link? FYI, the Sun box is showing... (2 Replies)
Discussion started by: bashdem
2 Replies

3. AIX

interface collisions on ethernet nic

Hi, is there any method to check the interface collisions on ethernet NIC in AIX. I know that in Solaris it's netstat -i but I've written that in AIX it doesn't show this. Thanks&regards, p (1 Reply)
Discussion started by: pitmod
1 Replies
MD5(1)							    BSD General Commands Manual 						    MD5(1)

NAME
md5, sha1, sha256, sha512, rmd160 -- calculate a message-digest fingerprint (checksum) for a file SYNOPSIS
md5 [-pqrtx] [-c string] [-s string] [file ...] sha1 [-pqrtx] [-c string] [-s string] [file ...] sha256 [-pqrtx] [-c string] [-s string] [file ...] sha512 [-pqrtx] [-c string] [-s string] [file ...] rmd160 [-pqrtx] [-c string] [-s string] [file ...] DESCRIPTION
The md5, sha1, sha256, sha512 and rmd160 utilities take as input a message of arbitrary length and produce as output a ``fingerprint'' or ``message digest'' of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given prespecified target message digest. The MD5, SHA-1, SHA-256, SHA-512 and RIPEMD-160 algo- rithms are intended for digital signature applications, where a large file must be ``compressed'' in a secure manner before being encrypted with a private (secret) key under a public-key cryptosystem such as RSA. MD5 has been completely broken as far as finding collisions is concerned, and should not be relied upon to produce unique outputs. This also means that MD5 should not be used as part of a cryptographic signature scheme. At the current time (2014-05-17) there is no publicly known method to ``reverse'' MD5, i.e., to find an input given a hash value. SHA-1 currently (2014-05-17) has no known collisions, but an attack has been found which is faster than a brute-force search, placing the security of SHA-1 in doubt. It is recommended that all new applications use SHA-256 instead of one of the other hash functions. The following options may be used in any combination and must precede any files named on the command line. The hexadecimal checksum of each file listed on the command line is printed after the options are processed. -c string Compare the digest of the file against this string. (Note that this option is not yet useful if multiple files are specified.) -s string Print a checksum of the given string. -p Echo stdin to stdout and append the checksum to stdout. -q Quiet mode -- only the checksum is printed out. Overrides the -r option. -r Reverses the format of the output. This helps with visual diffs. Does nothing when combined with the -ptx options. -t Run a built-in time trial. -x Run a built-in test script. EXIT STATUS
The md5, sha1, sha256, sha512 and rmd160 utilities exit 0 on success, 1 if at least one of the input files could not be read, and 2 if at least one file does not have the same hash as the -c option. SEE ALSO
cksum(1), md5(3), ripemd(3), sha(3), sha256(3), sha512(3) R. Rivest, The MD5 Message-Digest Algorithm, RFC1321. J. Burrows, The Secure Hash Standard, FIPS PUB 180-2. D. Eastlake and P. Jones, US Secure Hash Algorithm 1, RFC 3174. RIPEMD-160 is part of the ISO draft standard "ISO/IEC DIS 10118-3" on dedicated hash functions. Secure Hash Standard (SHS): http://csrc.nist.gov/cryptval/shs.html. The RIPEMD-160 page: http://www.esat.kuleuven.ac.be/~bosselae/ripemd160.html. ACKNOWLEDGMENTS
This program is placed in the public domain for free general use by RSA Data Security. Support for SHA-1 and RIPEMD-160 has been added by Oliver Eikemeier <eik@FreeBSD.org>. BSD
May 17, 2014 BSD
All times are GMT -4. The time now is 11:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy