Cryptography Basics for the Aspiring Hacker
As hackers, we are often faced with the hurdle of cryptography and encryption. Every cyber security engineer worth their pocket protector understands that encryption make the hacker/attacker's task much more difficult. In some cases it may be useful to the hacker, to hide actions and messages.
Many applications and protocols use encryption to maintain confidentiality and integrity of data. To be able to crack passwords and encrypted protocols such as SSL and wireless, you need to have at least a basic familiarity with the concepts and terminology of cryptography and encryption.
â€‹
To many new hackers, all the concepts and terminology of cryptography can be a bit overwhelming and opaque. To start, cryptography is the science and art of hiding messages so that they are confidential, then "unhiding" them so that only the intended recipient can read them. Basically, we can say that cryptography is the science of secret messaging.
â€‹
With this brief overview for the newcomer, I hope to lift the fog that shrouds this subject and shed a tiny bit of light on cryptography. I intend this simply to be a quick and cursory overview of cryptography for the novice hacker, not a treatise on the algorithms and mathematics of encryption. I'll try to familiarize you with the basic terminology and concepts so that when you read about hashing, wireless cracking, or password cracking and the encryption technologies are mentioned, you have some grasp of what is being addressed.
â€‹
Don't get me wrong, I don't intend to make you a cryptographer here (that would take years), but simply to help familiarize the beginner with the terms and concepts of cryptography so as to help you become a credible hacker.
I will attempt to use as much plain English to describe these technologies as possible, but like everything in IT, there is a very specialized language for cryptography and encryption. Terms like cipher, plaintext, ciphertext, keyspace, block size, and collisions can make studying cryptography a bit confusing and overwhelming to the beginner. I will use the term "collision," as there really is no other word in plain English that can replace it.
â€‹
Let's get started by breaking encryption into several categories.
â€‹
Types of Cryptography
â€‹
There are several ways to categorize encryption, but for our purposes here, I have broken them down into four main areas (I'm sure cryptographers will disagree with this classification system, but so be it).
â€‹

Symmetric Encryption

Asymmetric Encryption

Hashes

Wireless
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
A Word About Key Size
â€‹
In the world of cryptography, size does matter! In general, the larger the key, the more secure the encryption. This means that AES with a 256bit key is stronger than AES with an 128bit key and likely will be more difficult to crack. Within the same encryption algorithm, the larger the key, the stronger the encryption.
â€‹
It does not necessarily mean that larger keys mean stronger encryption between encryption algorithms. Between algorithms, the strength of the encryption is dependent on both the particulars of the algorithm AND the key size.
â€‹
Symmetric Cryptography
â€‹
Symmetric cryptography is where we have the same key at the sender and receiver. It is the most common form of cryptography. You have a password or "key" that encrypts a message and I have the same password to decrypt the message. Anyone else can't read our message or data.
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
Symmetric cryptography is very fast, so it is wellsuited for bulk storage or streaming applications. The drawback to symmetric cryptography is what is called the key exchange. If both ends need the same key, they need to use a third channel to exchange the key and therein lies the weakness. If there are two people who want to encrypt their communication and they are 12,000 miles apart, how do they exchange the key? This key exchange then is fraught with the all the problems of the confidentiality of the medium they choose, whether it be telephone, mail, email, facetoface, etc. The key exchange can be intercepted and render the confidentiality of the encryption moot.
â€‹
Some of the common symmetric algorithms that you should be familiar with are:
â€‹

DES  This was one of the original and oldest encryption schemes developed by IBM. It was found to be flawed and breakable and was used in the original hashing system of LANMAN hashes in early (pre2000) Windows systems.
â€‹

3DES  This encryption algorithm was developed in response to the flaws in DES. 3DES applies the DES algorithm three times (hence the name "triple DES") making it slightly more secure than DES.
â€‹

AES  Advanced Encryption Standard is not a encryption algorithm but rather a standard developed by National Institute for Standards and Technology (NIST). Presently, it is considered the strongest encryption, uses a 128, 196, or 256bit key and is occupied by the Rijndael algorithm since 2001. It's used in WPA2, SSL/TLS, and many other protocols where confidentiality and speed is important.
â€‹

RC4  This is a streaming (it encrypts each bit or byte rather than a block of information) cipher and developed by Ronald Rivest of RSA fame. Used in VoIP and WEP.
â€‹

Blowfish  The first of Bruce Schneier's encryption algorithms. It uses a variable key length and is very secure. It is not patented, so anyone can use it without license.
â€‹

Twofish  A stronger version of Blowfish using a 128 or 256bit key and was strong contender for AES. Used in Cryptcat and OpenPGP, among other places. It also is in the public domain without a patent.
â€‹
Asymmetric Cryptography
â€‹
Asymmetric cryptography uses different keys on both ends of the communication channel. Asymmetric cryptography is very slow, about 1,000 times slower than symmetric cryptography, so we don't want to use it for bulk encryption or streaming communication. It does, however, solve the key exchange problem. Since we don't need to have the same key on both ends of a communication, we don't have the issue of key exchange.
â€‹
Asymmetric cryptography is used primarily when we have two entities unknown to each other that want to exchange a small bit of information, such as a key or other identifying information, such as a certificate. It is not used for bulk or streaming encryption due to its speed limitations.
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
Some of common asymmetric encryption schemes you should be familiar with are:
â€‹

DiffieHellman  Many people in the field of cryptography regard the DiffieHellman key exchange to be the greatest development in cryptography (I would have to agree). Without going deep into the mathematics, Diffie and Hellman developed a way to generate keys without having to exchange the keys, thereby solving the key exchange problem that plagues symmetric key encryption.

RSA  Rivest, Shamir, and Adleman is a scheme of asymmetric encryption that uses factorization of very large prime numbers as the relationship between the two keys.
â€‹

PKI  Public key infrastructure is the widely used asymmetric system for exchanging confidential information using a private key and a public key.
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹

ECC  Elliptical curve cryptography is becoming increasing popular in mobile computing as it efficient, requiring less computing power and energy consumption for the same level of security. ECC relies upon the shared relationship of two functions being on the same elliptical curve.
â€‹

PGP  Pretty Good Privacy uses asymmetric encryption to assure the privacy and integrity of email messages.
â€‹
Hashes
â€‹
Hashes are oneway encryption. A message or password is encrypted in a way that it cannot be reversed or unencrypted. You might wonder, "What good would it do us to have a something encrypted and then not be able to decrypt it?" Good question!
â€‹
When the message is encrypted it creates a "hash" that becomes a unique, but indecipherable signature for the underlying message. Each and every message is encrypted in a way that it creates a unique hash. Usually, these hashes are a fixed length (an MD5 hash is always 32 characters). In that way, the attacker can not decipher any information about the underlying message from the length of the hash. Due to this, we don't need to know the original message, we simply need to see whether some text creates the same hash to check its integrity (unchanged).
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
â€‹
This is why hashes can be used to store passwords. The passwords are stored as hashes and then when someone tries to log in, the system hashes the password and checks to see whether the hash generated matches the hash that has been stored. In addition, hashes are useful for integrity checking, for instance, with file downloads or system files.
In the world of encryption and hashing, a "collision" is where two different input texts produce the same hash. In other words, the hash is not unique. This can be an issue when we assume that all the hashes are unique such as in certificate exchanges in SSL. NSA used this property of collisions in the Stuxnet malware to provide it with what appeared to be a legitimate Microsoft certificate. Hash algorithms that produce collisions, as you might guess, are flawed and insecure.
â€‹
These are the hashes you should be familiar with.
â€‹

MD4  This was an early hash by Ron Rivest and has largely been discontinued in use due to collisions.
â€‹

MD5  The most widely used hashing system. It's 128bit and produces a 32character message digest.
â€‹

SHA1 Developed by the NSA, it is more secure than MD5, but not as widely used. It has 160bit digest which is usually rendered in 40character hexadecimal. Often used for certificate exchanges in SSL, but because of recently discovered flaws, is being deprecated for that purpose.
â€‹
Wireless Cryptography
â€‹
Wireless cryptography has been a favorite of my readers as so many here are trying to crack wireless access points. As you might guess, wireless cryptography is symmetric (for speed), and as with all symmetric cryptography, key exchange is critical.
â€‹

WEP  This was the original encryption scheme for wireless and was quickly discovered to be flawed. It used RC4, but because of the small key size (24bit), it repeated the IV about every 5,000 packets enabling easy cracking on a busy network using statistical attacks.
â€‹

WPA  This was a quick fix for the flaws of WEP, adding a larger key and TKIP to make it slightly more difficult to crack.
â€‹

WPA2PSK  This was the first of the more secure wireless encryption schemes. It uses a preshared key (PSK) and AES. It then salts the hashes with the AP name or SSID. The hash is exchanged at authentication in a fourway handshake between the client and AP.
â€‹

WPA2Enterprise  This wireless encryption is the most secure. It uses a 128bit key, AES, and a remote authentication server (RADIUS).
â€‹
â€‹â€‹
I hope you keep coming back, my rookie hackers, as we continue to explore the wonderful world of information security and hacking!