Large Key Sizes and the Security of Password-Based Cryptography

Large Key Sizes and the Security of Password-Based Cryptography

Kent D. Boklan (Queens College, USA)
DOI: 10.4018/978-1-60960-200-0.ch005
OnDemand PDF Download:
List Price: $37.50


We expose a potential vulnerability in the common use of password-based cryptography. When employing a user-chosen password to generate cryptographic keys which themselves are larger than the digest size of the underlying hash function, a part of the resulting key is produced deterministically and this, in turn, may lead to an exploitable weakness.
Chapter Preview

Password-Based Security

Password-Based Encryption (PBE) derives an encryption key (see the Appendix for a Glossary of Technical Terms) from a user-assigned password; it is most commonly used to encrypt files which are stored locally. The Java Cryptography Extension (JCE) provides one framework for PBE. The Bouncy Castle cryptographic API (Bouncy Castle) is another (for both Java and C#). Coupled with a suite of available symmetric encryption schema from which to choose, one has all that is needed to protect data in such a way as that “only” the user in possession of the password can gain access.

Password-based security is invariably less secure than ideal. The primary reason for this is that there is insufficient entropy (i.e. number of bits of randomness) in a password to generate a strong cryptographic key. Keys used in symmetric encryption protocols should be randomly generated; when they are derived from a user password, there’s almost always a markèd drop in security. Effective randomness in password selection is very difficult to achieve and still more difficult to demand. (We differentiate between keys for symmetric cryptography and for public key cryptography; the private keys for the latter class are mathematically dependent upon the public keys.) One of the hallmarks of cryptographic best practices is having secrets that are not biased so no information may be gained by an attacker; attacks can be mounted given even slight predisposition. Hidden Markov models are one tool used to exploit such weaknesses and build likelihood distribution models. NIST Special Publication 800-63 (NIST, 2006) suggests than an 8 character, user-chosen password, contains between 18 and 30 bits of entropy. Since an ASCII character can be regarded as a 7 bit number, a truly random 8 character password would has a (maximum) entropy of 56 bits. The average password, so, is not very random, at all. A phishing attack on MySpace reported in late 2006 (Schneier, 2006) gave further insight into password composition for 34,000 users. The good news for security: ‘password’ was no longer the most commonly used password (it ranked 4th). The bad news: it’s ‘password1’ (used in about 1 in ever 450 accounts). The average password length was 8 characters and 1 in 6 used an anemic 6 or fewer characters. MySpace did not place any structural requirements on passwords and it seems that users today have been led to believe that adding a digit to a password enhances security. This is, unfortunately, not a practical truth. Of the MySpace passwords, about 1 in 5 were lower case letters followed by the single digit ‘1’. In all, 8% of users had a password that was a single dictionary word followed by a ‘1’. This sets the stage for a clear attack: assume a password length of 8 characters with a final digit of 1. Now you have only 7 characters to figure out and you’ve removed about 99% of the cases. (When users are required to change their passwords, they cycle the ‘1’ to a ‘2,’ a predictable path of least resistance – so, very often, no security is gained.) Forcing password structure requirements (such as the necessity of containing a number) goes to lessen password entropy and this, in turn, makes data secured by PBE less secure.

Complete Chapter List

Search this Book: