Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was looking at using the encrypt option in an application but I've read some comments saying it is not so secure because it uses static keys.

How easy is it to break static key encryption? Does it require lots of data points or just lots of time?

share|improve this question

A static key is one you use more than once over a long period of time. It is often considered less secure than using an ephemeral key (that changes each time) because:

  • An eavesdropper gets more material to work with.
  • If an attacker breaks the key, they can decrypt multiple messages.
  • It gives the attacker the possibility of arranging a known plaintext attack.

However, static keys are often easier to implement. And in some cases none of the above matter. And security is a process, not just using the strongest possible algorithm. (Or else we'd all use one-time pads!)

So the answer is "sometimes more, sometimes less, it depends".

share|improve this answer
Also, if there's no nonce at the beginning of the message, an attacker may also be able to compare two messages for equivalence, or (assuming a cipher that is an XOR with keystream), guess the content of two messages and recover the keystream. – MZB May 3 '12 at 23:17

If the key is part of the application, it will be very easy for an attacker to use a debugger to extract it. He does not need to break any encryption at all.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.