| Revision as of 16:42, 17 September 2004 editKbh3rd (talk | contribs)Extended confirmed users31,490 edits more on key strength relative to brute force searches← Previous edit | Latest revision as of 19:06, 30 January 2022 edit undoTavix (talk | contribs)Autopatrolled, Administrators75,478 edits R with history | ||
| (14 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
| #REDIRECT ] | |||
| In the field information system security a '''brute-force attack''' is a method to determine the key of an encrypted message. While simple to implement, it is a ] method of attack. A Brute-Force attack is similar to a ]. | |||
| {{R from other hyphenation}} | |||
| The implementation of such an attack involves the generation of a series of ] either ]ically or from a predetermined list. The latter is also known as a ]. <!-- IMHO a dictionary attack and a brute-force attack are two separate things. kbh3rd --> The generated keys and the chosen ] are applied to the message to produce a ]. Each passage of ] must be ] to determine if it is a valid and therefore properly decrypted message. | |||
| {{R with history}} | |||
| This is an extremely time-consuming task, the effort for which increases exponentially with the size of the key. Cracking a message with a relatively miniscule 6-digit ] key has <math>62^6</math> possible solutions, each of which must be run through the verfication process. | |||
| The benefit of a Brute-Force attack is that, given enough time, the correct key is guaranteed to be found. The relative security of a ] system can be measured by the mean search time required to find a key by brute force, and the security of an encrypted message may be expressed as the expected number of years required to determine its encryption key using brute force. This time decreases with increases in the power of computers. The decreasing cost and increasing power of computing resources has caused the ] to propose withdrawing the 56-]-keyed ] as an encryption standard in ]. | |||
| Specifics of Brute-force methods can be found at ]. | |||
Latest revision as of 19:06, 30 January 2022
Redirect to:
- From an alternative hyphenation: This is a redirect from a title with an alternative hyphenation of the target name. Pages that link to this redirect may be updated to link directly to the target page if that results in an improvement of the text. Do not "fix" such links if they are not broken. Also, these links should not be replaced with piped links.
- With history: This is a redirect from a page containing substantive page history. This page is kept as a redirect to preserve its former content and attributions. Please do not remove the tag that generates this text (unless the need to recreate content on this page has been demonstrated), nor delete this page.
- This template should not be used for redirects having some edit history but no meaningful content in their previous versions, nor for redirects created as a result of a page merge (use {{R from merge}} instead), nor for redirects from a title that forms a historic part of Misplaced Pages (use {{R with old history}} instead).