From 558924e88ec65db1f87e6d76d064112fcf819cf9 Mon Sep 17 00:00:00 2001 From: Hrushikesh Salunkhe Date: Wed, 4 Mar 2020 16:30:11 +0530 Subject: [PATCH] Typo fix users passwords changed to users' passwords --- .../_includes/about/authentication/password-storage.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/src/docs/asciidoc/_includes/about/authentication/password-storage.adoc b/docs/manual/src/docs/asciidoc/_includes/about/authentication/password-storage.adoc index 6fe994c7fd..018fa0dc16 100644 --- a/docs/manual/src/docs/asciidoc/_includes/about/authentication/password-storage.adoc +++ b/docs/manual/src/docs/asciidoc/_includes/about/authentication/password-storage.adoc @@ -12,7 +12,7 @@ Throughout the years the standard mechanism for storing passwords has evolved. In the beginning passwords were stored in plain text. The passwords were assumed to be safe because the data store the passwords were saved in required credentials to access it. However, malicious users were able to find ways to get large "data dumps" of usernames and passwords using attacks like SQL Injection. -As more and more user credentials became public security experts realized we needed to do more to protect users passwords. +As more and more user credentials became public security experts realized we needed to do more to protect users' passwords. Developers were then encouraged to store passwords after running them through a one way hash such as SHA-256. When a user tried to authenticate, the hashed password would be compared to the hash of the password that they typed.