Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Ask Slashdot: Why does brute force work on encryption?

Anonymous Coward writes | about 10 months ago

0

An anonymous reader writes "When data is encrypted, it becomes a garble of "random" characters. With brute force, the attacker keeps trying new keys until one is found that unlocks the encryption. But how does the attacker know that they have succeeded? What is it that tells them that the result they have now is coherent? Please help inform me and others who don't know as much about encryption. Because it seems to me that if a file is encrypted twice, the attacker would never be able to see coherent data from the first unlocking. And apparently that's not true. Why? And why can't encryption be made more resistant to brute force?"

cancel ×

0 comments

Sorry! There are no comments related to the filter you selected.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>