Skip to content
This repository was archived by the owner on Jan 25, 2025. It is now read-only.

Commit f1a0f2f

Browse files
authored
Merge pull request #11 from Keyspace-cloud/readme-tweaks
Readme tweaks
2 parents 6a2faf5 + ed1393f commit f1a0f2f

File tree

3 files changed

+3
-1
lines changed

3 files changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,9 @@ Keyspace uses end-to-end encryption to secure all user data (Logins, Notes, Card
5050

5151
### Signature based authentication scheme
5252

53-
Most password managers transmit a hash of users master password for authentication purposes. [Bitwarden - See page 9](https://bitwarden.com/images/resources/security-white-paper-download.pdf) Keyspace uses a challenge-response based authentication scheme to eliminate users master password hashes being stored on the backend. The client simply signs cryptographic challenge and sends it to the backend. Password hashes never cross the wire.
53+
_Read more: [Bitwarden Security White Paper (page 9)](https://bitwarden.com/images/resources/security-white-paper-download.pdf)_
54+
55+
Most password managers transmit a hash of users master password for authentication purposes. Keyspace uses a challenge-response based authentication scheme to eliminate users master password hashes being stored on the backend. The client simply signs cryptographic challenge and sends it to the backend. Password hashes never cross the wire.
5456

5557
### Deterministic Key derivation
5658

-208 KB
Loading
-990 KB
Loading

0 commit comments

Comments
 (0)