Cryptographic Fingerprint (SHA 256 Hash) - Revision history

Lori at 18:28, 31 July 2020

2020-07-31T18:28:03Z

Lori: Lori moved page Mobile Password Safe - to Cryptographic Fingerprint (SHA 256 Hash)

2020-04-20T19:03:50Z

Lori moved page Mobile Password Safe - to Cryptographic Fingerprint (SHA 256 Hash)

Lori: Lori moved page Mobile Password Safe - Cryptographic Fingerprint (SHA 256 Hash) to Mobile Password Safe -

2020-04-20T19:02:43Z

Lori moved page Mobile Password Safe - Cryptographic Fingerprint (SHA 256 Hash) to Mobile Password Safe -

Lori at 17:13, 20 April 2020

2020-04-20T17:13:37Z

Lori: Create Mobile Password Safe Cryptographic Fingerprint page

2020-04-16T19:54:30Z

Create Mobile Password Safe Cryptographic Fingerprint page

New page

The easiest way to describe a '''Cryptographic Fingerprint''' (aka Hash) is that it generates a very large unique number for any given input. That is, if I have a 2GB file and I change 1 character in the file, the hashes will be very different.

Hashes are one-way; this means that if someone sees the hash of your password it is extremely difficult to determine the password from the hash; only a brute-force method will suffice.

This makes the SHA 256 Hash a good choice which to determine if your password is correct or not after it is first entered. We run the hash on your password once, store it, and subsequently compare the hash of your password with the original hash we stored.

It is currently industry best practice to store passwords using the SHA 256 Algorithm.

[http://en.wikipedia.org/wiki/SHA256 Wikipedia Article on SHA 256]

← Older revision		Revision as of 17:13, 20 April 2020
Line 8:		Line 8:

	[http://en.wikipedia.org/wiki/SHA256 Wikipedia Article on SHA 256]		[http://en.wikipedia.org/wiki/SHA256 Wikipedia Article on SHA 256]
		+
		+	[[Category:Mobile Password Safe]]

@@ Line 3: / Line 3: @@
 Hashes are one-way; this means that if someone sees the hash of your password it is extremely difficult to determine the password from the hash; only a brute-force method will suffice.
-This makes the SHA 256 Hash a good choice which to determine if your password is correct or not after it is first entered. We run the hash on your password once, store it, and subsequently compare the hash of your password with the original hash we stored.
+This makes the [[SHA-256|SHA 256]] Hash a good choice which to determine if your password is correct or not after it is first entered. We run the hash on your password once, store it, and subsequently compare the hash of your password with the original hash we stored.
 It is currently industry best practice to store passwords using the SHA 256 Algorithm.

← Older revision	Revision as of 19:03, 20 April 2020
(No difference)

← Older revision	Revision as of 19:02, 20 April 2020
(No difference)