From def2d163f81a6dc2d2c353ba17063c1fce094f1b Mon Sep 17 00:00:00 2001 From: Saguine Date: Wed, 7 Jan 2015 07:27:57 +0200 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index aeb6941..d56aeb9 100644 --- a/README.md +++ b/README.md @@ -38,9 +38,9 @@ a session if data has been changed, as changes can only be saved when the user i ## Things to consider -- With SHA-512 hashes taking up 64 bytes of storage, it's possible to accomodate a million accounts in under 64MB. +- With SHA-512 hashes taking up 64 bytes of storage, it's possible to accomodate a million accounts in just 64MB. - When considering multiple servers with multiple backup points, it's possible to simply make the hash database public, masking transfers to backup servers by crowdsourcing false leads. - A correctly implemented no- system would still be vulnerable to a stealthy server compromise; that is, a server known to use the no- system is compromised and changes the layer which implements such, saving data somewhere else when users log in. -- Even considering the above, a stealth compromised server never gives information about the users who have not logged in. \ No newline at end of file +- Even considering the above, a stealth compromised server never gives information about the users who have not logged in.