Diffie-Hellman Key Exchange
First published at:
Diffie-Hellman Key Exchange is a popular mathematical key exchange algorithm. It allows two parties to establish a ‘key’ over an insecure medium such as the internet. As you will see, it doesn’t matter whether the intercepting party captures each piece of transmitted information, they will not be able to break the key in any way, other than the usual brute force method.
Diffie-Hellman Key Exchange is not an encryption method, it is generall but not always used pre encryption to decide on a shared encryption key.
We will call the communicating parties Bill and Ben. Let Roger be the intercepting party. You can work out these calculations on a calculator:
Bill and Ben transmit and agree on a public prime number (p) and a ‘generator’ (g) which is an integer less than ‘p’. Bill now decides on a random private number (a) which he does not transmit, Ben also agrees on a random private number (b) which he does not transmit either.
In this example, Bill and Ben decide that:
Roger catches p(137) and g(13)
Bill decides privately that a=31
Ben decides privately that b=23
In actual fact these numbers will be much larger to hinder brute force. We’re going to use small numbers in our example though.
Bill now computes:
j = (ga)modp [ programatically j=(g^a)%p]
j = (1331)mod137
j = 20
Ben now computes:
k = (gb)modp [ programatically k=(g^b)%p ]
k = (1323)mod137
k = 24
Ben now transmits k to Bill, and Bill transmits j to Ben
Roger captures (j)20 and (k)24
Bill now computes:
x = kamodp [programatically =(k^a)%p
x = 2431mod137
x = 91
Bill now knows that the shared encryption key is 72. He does not [need to] transmit it.
x = jbmodp [programatically =(j^b)%p
x = 2023mod137
x = 92
Ben also now knows that the shared encryption key is 72. He does not [need to] transmit it.
At this point, expand outwards:
x = 92
x = jbmodp = kamodp
((ga)modp)bmodp == ((gb)modp)amodp
Despite the fact that Roger has caught each individual transmission, j, k, g, and p, he can not work out x.
Now that both sides know the key, we can now agree that they’re going to encrypt using AAE - Adam’s Amazing Encryption.
Bob takes his phrase to encrypt - “password” and adds ‘72′ to each character using the ASCII alphabet:
Bob can now turn his phrase to a hex string:
And then add 72 to each character, making sure it wraps around 255:
Ben can now decrypt using the opposite method.
In actual fact, not only would the key be substantially longer than ‘72′, but our encryption algorithm of choice ‘AAE’ would also be replaced with something more cryptographically sound :-) - Possibly RC4
|Where's That Pesky Hidden Word?||Aug 28, 2015|
|A Project to Guarantee Better Security for Open-Source Projects||Aug 27, 2015|
|Concerning Containers' Connections: on Docker Networking||Aug 26, 2015|
|My Network Go-Bag||Aug 24, 2015|
|Doing Astronomy with Python||Aug 19, 2015|
|Build a “Virtual SuperComputer” with Process Virtualization||Aug 18, 2015|
- Concerning Containers' Connections: on Docker Networking
- Problems with Ubuntu's Software Center and How Canonical Plans to Fix Them
- A Project to Guarantee Better Security for Open-Source Projects
- Where's That Pesky Hidden Word?
- Firefox Security Exploit Targets Linux Users and Web Developers
- My Network Go-Bag
- Doing Astronomy with Python
- Three More Lessons
- Build a “Virtual SuperComputer” with Process Virtualization
- Calling All Linux Nerds!