Skip to content

Commit 7ddaec2

Browse files
committed
Fixed a list in the README
Signed-off-by: Jeff Nickoloff <jeff@allingeek.com>
1 parent afdeda3 commit 7ddaec2

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ The second big question is, "What should my authentication protocol look like?"
1111
In an ideal situation you should be able to authenticate unique instances of a client service. It is unlikely that you will want to do so if you use preshared keys and a user management system that is painful to scale. More often than not, developers end up using a single password for each client service. In that situation it becomes more difficult to determine when a key has been compromised and more likely that a key will be compromised.
1212

1313
Key management nightmares include:
14+
1415
1. cleartext keys shipped with code
1516
2. encrypted keys shipped with code (how do you decrypt them?)
1617
3. cleartext keys co-deployed along side code using configuration management tools

0 commit comments

Comments
 (0)