SHA - Revision history

Franks: /* Using SHA256+ in Linux */

2021-02-07T13:08:59Z

Using SHA256+ in Linux

← Older revision		Revision as of 06:08, 7 February 2021
Line 46:		Line 46:

	=== Using SHA256+ in Linux ===		=== Using SHA256+ in Linux ===

			On Debian/Ubuntu:

			$ shasum -a 256 /dev/null
			e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b936ca495991b7852b855 /dev/null
			# -a, --algorithm 1 (default), 224, 256, 384, 512, 512224, 512256

	In this example it's OpenSuse 10.3, one has to use the openssl package:		In this example it's OpenSuse 10.3, one has to use the openssl package:

Pbug: /* Using sha256+ in Linux */

2009-05-10T20:29:35Z

Using sha256+ in Linux

← Older revision		Revision as of 13:29, 10 May 2009
Line 45:		Line 45:


	=== Using ~~sha256~~+ in Linux ===		=== Using SHA256+ in Linux ===

	In this example it's OpenSuse 10.3, one has to use the openssl package:		In this example it's OpenSuse 10.3, one has to use the openssl package:

Pbug: Sha256 in Linux

2009-05-10T20:28:10Z

Sha256 in Linux

← Older revision		Revision as of 13:28, 10 May 2009
Line 43:		Line 43:
	$ digest -v -a sha512 /dev/null		$ digest -v -a sha512 /dev/null
	sha512 (/dev/null) = cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e		sha512 (/dev/null) = cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e


			=== Using sha256+ in Linux ===

			In this example it's OpenSuse 10.3, one has to use the openssl package:

			> openssl dgst -sha256 /dev/null
			SHA256(/dev/null)= e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
			> openssl dgst -sha512 /dev/null
			SHA512(/dev/null)= cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e

			There doesn't seem to be a sha384 though.

Pbug: FreeBSD 7.0 and Solaris 10

2009-05-10T20:17:47Z

FreeBSD 7.0 and Solaris 10

← Older revision		Revision as of 13:17, 10 May 2009
Line 23:		Line 23:

	The checksum is against the binary, NOT the hexdump of normal sha512.		The checksum is against the binary, NOT the hexdump of normal sha512.


			=== SHA256 in FreeBSD ===

			FreeBSD 7.0-stable has a sha256 program:

			$ sha256 /dev/null
			SHA256 (/dev/null) = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855


			=== SHA256+ in Solaris 10 ===

			Use the digest command:

			$ digest -v -a sha256 /dev/null
			sha256 (/dev/null) = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
			$ digest -v -a sha384 /dev/null
			sha384 (/dev/null) = 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b
			$ digest -v -a sha512 /dev/null
			sha512 (/dev/null) = cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e

Pbug: /* Using SHA256+ in OpenBSD */ and NetBSD

2009-05-10T20:08:50Z

Using SHA256+ in OpenBSD: and NetBSD

← Older revision		Revision as of 13:08, 10 May 2009
Line 6:		Line 6:
	SHA1 (/etc/passwd) = c7ae5b7306797d9f1f5fba85683cdd36ba8d1a08		SHA1 (/etc/passwd) = c7ae5b7306797d9f1f5fba85683cdd36ba8d1a08

	=== Using SHA256+ in OpenBSD ===		=== Using SHA256+ in OpenBSD and NetBSD ===

	As of OpenBSD 4.5 the cksum command does SHA256, SHA384 and SHA512 the command is done like so:		As of OpenBSD 4.5 and NetBSD 4.0 the cksum command does SHA256, SHA384 and SHA512 the command is done like so:

	$ cksum -a sha256 /dev/null		$ cksum -a sha256 /dev/null
Line 17:		Line 17:
	SHA512 (/dev/null) = cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e		SHA512 (/dev/null) = cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e

	A neat feature is the -b flag in cksum which outputs the SHA checksum in base64:		A neat feature in OpenBSD is the -b flag in cksum which outputs the SHA checksum in base64:

	$ cksum -a sha512 -b /dev/null		$ cksum -a sha512 -b /dev/null

Pbug: /* Using SHA256+ in OpenBSD */

2009-05-10T17:53:00Z

Using SHA256+ in OpenBSD

← Older revision		Revision as of 10:53, 10 May 2009
Line 22:		Line 22:
	SHA512 (/dev/null) = z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==		SHA512 (/dev/null) = z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==

	The checksum is against the binary ~~representation not~~ the hexdump of normal sha512.		The checksum is against the binary, NOT the hexdump of normal sha512.

Pbug: sha256 -> sha512 in OpenBSD

2009-05-10T17:49:32Z

sha256 -> sha512 in OpenBSD

← Older revision		Revision as of 10:49, 10 May 2009
Line 5:		Line 5:
	$ sha1 /etc/passwd		$ sha1 /etc/passwd
	SHA1 (/etc/passwd) = c7ae5b7306797d9f1f5fba85683cdd36ba8d1a08		SHA1 (/etc/passwd) = c7ae5b7306797d9f1f5fba85683cdd36ba8d1a08

			=== Using SHA256+ in OpenBSD ===

			As of OpenBSD 4.5 the cksum command does SHA256, SHA384 and SHA512 the command is done like so:

			$ cksum -a sha256 /dev/null
			SHA256 (/dev/null) = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
			$ cksum -a sha384 /dev/null
			SHA384 (/dev/null) = 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b
			$ cksum -a sha512 /dev/null
			SHA512 (/dev/null) = cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e

			A neat feature is the -b flag in cksum which outputs the SHA checksum in base64:

			$ cksum -a sha512 -b /dev/null
			SHA512 (/dev/null) = z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==

			The checksum is against the binary representation not the hexdump of normal sha512.

Frankk at 15:52, 27 October 2005

2005-10-27T15:52:38Z

← Older revision		Revision as of 08:52, 27 October 2005
Line 1:		Line 1:
	SHA-0 (Secure Hash Algorithm) was a proposal by the U.S. government that was replaced by SHA-1 in FIPS 180-1. SHA-1 addresses the weakness found in SHA-0 by adding an additional circular shift operation. SHA-1 has [http://theory.csail.mit.edu/~yiqun/shanote.pdf a reported weakness] as far as [[hash collision]]s are concerned and awareness should be raised if you are implementing it.		SHA-0 (Secure Hash Algorithm) was a proposal by the U.S. government that was replaced by SHA-1 in FIPS 180-1. SHA-1 addresses the weakness found in SHA-0 by adding an additional circular shift operation, thus deprecated SHA-0. SHA-1 has [http://theory.csail.mit.edu/~yiqun/shanote.pdf a reported weakness] as far as [[hash collision]]s are concerned and awareness should be raised if you are implementing it.

	If you have the sha1 application installed, you can make use of the command like so:		If you have the sha1 application installed, you can make use of the command like so:

Frankk at 15:51, 27 October 2005

2005-10-27T15:51:45Z

← Older revision		Revision as of 08:51, 27 October 2005
Line 1:		Line 1:
	SHA-0 (Secure Hash Algorithm) was a proposal by the U.S. government that was replaced by SHA-1 in FIPS 180-1. SHA-1 addresses the weakness found in SHA-0 by adding an additional circular shift operation. SHA-1 has [http://theory.csail.mit.edu/~yiqun/shanote.pdf a reported weakness] as far as [[hash collision]]s are concerned and awareness should be raised if you are implementing it.		SHA-0 (Secure Hash Algorithm) was a proposal by the U.S. government that was replaced by SHA-1 in FIPS 180-1. SHA-1 addresses the weakness found in SHA-0 by adding an additional circular shift operation. SHA-1 has [http://theory.csail.mit.edu/~yiqun/shanote.pdf a reported weakness] as far as [[hash collision]]s are concerned and awareness should be raised if you are implementing it.

	~~In [[OpenBSD]]~~ you can make use of the ~~sha1~~ command like so:		If you have the sha1 application installed, you can make use of the command like so:

	$ sha1 /etc/passwd		$ sha1 /etc/passwd
	SHA1 (/etc/passwd) = c7ae5b7306797d9f1f5fba85683cdd36ba8d1a08		SHA1 (/etc/passwd) = c7ae5b7306797d9f1f5fba85683cdd36ba8d1a08

Pbug at 10:32, 27 October 2005

2005-10-27T10:32:50Z

← Older revision		Revision as of 03:32, 27 October 2005
Line 1:		Line 1:
	SHA-0 (Secure Hash Algorithm) was a proposal by the U.S. government that was replaced by SHA-1 in FIPS 180-1. SHA-1 addresses the weakness found in SHA-0 by adding an additional circular shift operation. SHA-1 has [http://theory.csail.mit.edu/~yiqun/shanote.pdf a reported weakness] as far as [[hash collision]]s are concerned and awareness should be raised if you are implementing it.		SHA-0 (Secure Hash Algorithm) was a proposal by the U.S. government that was replaced by SHA-1 in FIPS 180-1. SHA-1 addresses the weakness found in SHA-0 by adding an additional circular shift operation. SHA-1 has [http://theory.csail.mit.edu/~yiqun/shanote.pdf a reported weakness] as far as [[hash collision]]s are concerned and awareness should be raised if you are implementing it.

			In [[OpenBSD]] you can make use of the sha1 command like so:

			$ sha1 /etc/passwd
			SHA1 (/etc/passwd) = c7ae5b7306797d9f1f5fba85683cdd36ba8d1a08