ZDNet UK


Skip to Main Content

ZDNet.co.uk - Winner of Best Business Website 2007
  1. Home
  2. News
  3. Blogs
  4. Reviews
  5. Prices
  6. Resources
  7. Community
  8. My ZDNet

 

ZDNet UK RSS Feeds


IT Jobs

Security threats Toolkit

Surveillance: How encryption works

Will Knight ZDNet.co.uk

Published: 27 Sep 1999 11:25 BST

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

At the heart of the debate is encryption technology. How does encryption work and why is it so important for our personal privacy? Will Knight provides insight.

What it is...

"Encrypted" information, in its simplest terms, is data made unintelligible by garbling it using a mathematical mixing process controlled by a special "key". Decryption reverses this action and makes the information readable again. This is easy to achieve if the key is available.

Without the key, accessing the encrypted information is extremely difficult in principle, and often impossible in practice.

For the last 50 years encryption has been largely used by governments to hide military and diplomatic information but it is now increasingly being used commercially for things such as cash machines, pay TV and even wireless burglar alarms.

What controversy?

The controversy surrounding access to encrypted data is rooted in the way in which two American academics, Whitfield Diffie and Martin Hellman, revolutionised encrypted communication in 1976 by inventing the concept of "public" and "private" keys (it is now known that the same ideas were discovered even earlier by GCHQ scientists but for reasons of national security were kept secret).

Public and private keys

A "key" in this context is a piece of data used to either encrypt or decrypt a piece of data or message.

In conventional encryption the same "secret key" is used for both encryption and decryption and is kept secret between the sender and recipient of a message. For secret information to pass between the sender and the recipient these keys must be available to both. If they are not, the information cannot be accessed.

Diffie and Hellman discovered that it is possible to have a pair of keys rather than a single key, so that when one key of a pair is used to garble information the other is needed to recover it. This means that knowing the encryption, or "public", key does not necessarily allow messages to be decrypted, since this requires the second pair. As a result, anyone who wants to receive encrypted messages can publish their public key with their name attached and invite others to use it to send them encrypted messages. They then use the other key of the pair -- which is kept secret -- to decrypt the messages.

The trick here is to find mathematical problems of sufficient complexity to ensure it would take an inordinate amount of time -- not to mention effort -- to use the public key to figure out the private one.

The first method for doing this was developed by the inventors of the RSA standard for public key cryptography, Rivest, Shamir and Adleman in 1979. These bright sparks suggested it should be possible to obtain key pairs by multiplying two very large secret prime numbers -- an easy task. But the opposite task, finding the two secret prime numbers from the result, is enormously difficult and can be made impractical by choosing sufficiently large numbers to start with.

There have since been developed a number of different mathematical problems used to link the public and private key, but the essential factor is the length of time it takes for them to be solved.

What's a "bit"?

Keys are often described in terms of "bits", for example, "40 bit keys".

Here the number of bits measures how difficult it is to recover encrypted information without requiring the private key.

In "secret key" encryption every bit added doubles, on average, the time taken to break a piece of encrypted information ("breaking" is a term used to describe recovering encrypted information without having the decryption key). With public key encryption -- using key pairs -- the difficulty also grows as the length of keys increases but in a different way.

So, the length of keys in bits is a broad measure of the complexity of the mathematical problem to be solved in order to break an encrypted message. The public and private keys of key pairs, for example, have to be much longer than the keys in secret key encryption.

It is important to realise, however, that even with modern computers it takes considerable computing power and time to break even the "40-bit" encryption currently permitted for unrestricted export from the US for public use.

In Part 2, an explanation of the National Criminal Intelligence Service's decryption goals.

Take me to Surveillance.

What do you think? Tell the Mailroom.

  • Email
  • Trackback
  • Clip Link
  • Print friendly Print with HP

Did you find this article useful?
28 out of 66 people found this useful


Full Talkback thread

0 comments

Company/Topic Alerts

Create a new alert from the list below:







Related Jobs

Database Consultant, Encryption, Oracle, SQL, DB2, Java, DBA, Surrey

Ideally you will have some experience with Cryptography / Cryptographic / Encryption technology, or at least have a strong appreciation of it. My ...

Mathematical Modeller to join Risk Managements Modelling team -London

Summary my client works wthin Software (Risk Products section) is currently looking for someone who wishes to be considered for a vacancy as a ...

C37335: Accenture Siebel Consultants

Experience of key areas of operational acceptance testing (such as Disaster Recover, Volume and Performance etc. Functional Oracle Siebel ...

Sentry Posts Blog

Mobile Linux Better For Mobile Busines...

Mobile Linux Better For Mobile Business Apps? Author: Eric Everson, MyMobiSafe.com As mobile Linux is carving it’s footprint on the future of mobile application development, the... More

Post a comment

DWP downplays security breach

The Department for Work and Pensions (DWP) has admitted that some of its staff have been forwarding passwords with password protected material. An email that was leaked on the 'Dizzy... More

Post a comment

How many headshots does one chairperso...

We got a strange request last week from the head of PR from Russian security experts Kaspersky. It seems although the company was very happy with the interview we recently carried with... More

Post a comment

Featured Talkback

On the contrary, if vendors were forced to stand behind their products it should increase innovation. It would force more, and better , testing before hitting the sales floor, resulting in fewer updates and less downtime for the consumer. At present the EULA removes responsibility from the vendor, and moves it to the user, which is a step backward. Make the vendor responsibility for their code.

By: ator1940

Read full story:
RSA: Vendor liability may stifle innovation