diff options
| author | Adrian C. (anrxc) <anrxc@sysphere.org> | 2010-05-17 21:41:36 +0200 |
|---|---|---|
| committer | Adrian C. (anrxc) <anrxc@sysphere.org> | 2010-05-17 21:41:36 +0200 |
| commit | ca1d8d79e55b7addc28dc442832815692b01b894 (patch) | |
| tree | 7f90d5bdd1f502d3c1bcf13e0a66f28d344ebcf1 /README | |
| parent | fdae848bba84ffdde70cb69696dd234e7b289b41 (diff) | |
| download | vicious-legacy-ca1d8d79e55b7addc28dc442832815692b01b894.tar.xz | |
README: cut on the security crap
Diffstat (limited to 'README')
| -rw-r--r-- | README | 5 |
1 files changed, 2 insertions, 3 deletions
@@ -342,9 +342,8 @@ the owner. Other than that we can not force all users to conform to one standard, one way of keeping it secure, like in some keyring. First let's clear why we simply don't encrypt the login information -and store it in ciphertext. Answer is simple, that is no more secure -than having it stored in plaintext. By exposing the algorithm anyone -can reverse the encryption steps. Some claim even that's better than +and store it in ciphertext. By exposing the algorithm anyone can +reverse the encryption steps. Some claim even that's better than plaintext but it's just security trough obscurity. Here are some ideas actually worth your time. Users that have KDE (or |