DOCSLIB.ORG

Password Implementation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Password Implementation Password Implementation Solaris uses the /etc/passwd file to keep track of every user on the system. As we have seen in the previous unit, the /etc/passwd file contains the username, the real name, identification information, and basic account information for each user. What the password file does not contain is the encrypted user password. That is stored in the /etc/shadow file. Encrypted Password System When Solaris requests your password, it needs some way of determining that the password that you type is the correct one. Under normal circumstances, most UNIX systems protect the passwords so that they could be accessed only by privileged users and operating system utilities. However, through accident, programming error, or deliberate act, the contents of the password file could occasionally become available to unprivileged users. In previous computer systems, passwords were stored in plain text where the file was appropriately restricted. The real danger posed by such systems explained Morris and Thompson is not that software problems might someday cause a problem, but that humans might accidently expose the passwords for the world to see. UNIX avoids this problem by not keeping actual passwords anywhere on the system. Instead UNIX stores a value that is generated by using the password to encrypt a block of zero bits with a one-way function called crypt(). The results of the calculation were traditionally stored in the /etc/passwd file. Solaris stores that information in the /etc/shadow file. When you try to log in to an account, the program /bin/login does not decrypt the stored password. Instead /bin/login takes the password that you typed, uses it to transform another block of zeros, and compares the newly transformed block with the block stored in the /etc/passwd file. If the two encrypted results match, the system lets you in. The security of this approach rests upon the strength of the encryption algorithm and the difficulty of guessing the user’s password. To date, the crypt() algorithm and its successors have proven highly resistant to attacks. The Traditional crypt() Algorithm The algorithm that traditional crypt() uses is based on the Data Encryption Standard (DES) of the National Institute of Standards and Technology (NIST). In normal operation, DES uses a 56-bit key (8 7-bit ASCII characters) to encrypt blocks of original text, or clear text, that are 64 bits in length. The resulting 64-bit blocks of encrypted text, or ciphertext, cannot be decrypted to the original cleartext without knowing the original 56-bit key. The UNIX crypt() function takes the user’s password as the encryption key and uses it to encrypt a 64-bit block of zeros. The resulting 64-bit block of ciphertext is then encrypted again with the user’s password. The process is repeated a total of 25 times. The final 64 bits are unpacked into a string of 11 printable characters that are stored in the shadow password file. Each of the 11 characters holds six bits of the results, represented as one of 64 characters in the set “.”, “/”, 0-9, A-Z, a-z, in that order. Thus the value 0 is represented as “.”, and the value 32 is the letter “U”. Note: Do not confuse the crypt() algorithm with the crypt encryption program. The crypt program uses a different encryption system from the crypt() algorithm. Although the source code to crypt() is readily available, no technique has been discovered or publicized to translate the encrypted password back into the original password. Such reverse translation may not even be possible. As a result, the only known way to defeat UNIX password security is via a brute-force attack, or by a dictionary attack. A dictionary attack is conducted by choosing likely passwords from a dictionary, encrypting them, and comparing the results with the value stored in /etc/shadow. This approach to breaking a cryptographic cipher is also called a key search or password cracking. It is made easier by the fact that DES uses only the first eight characters of the password as its key. Dictionaries need only contain passwords of eight characters or fewer. Robert Morris and Ken Thompson designed crypt() to make a key search computationally expensive. The idea was to make dictionary attacks take too long to be practical. At the time, software implementations of DES were quite slow. Iterating the encryption process 25 times made the process of encrypting a single password 25 times slower still. On the original PDP-11 processors upon which UNIX was designed, nearly a full second of computer time was required to encrypt a single password. To eliminate the possibility of using DES hardware encryption chips, which were a thousand times faster than software running on a PDP- 11, Morris and Thompson modified the DES tables used by their software implementation, rendering the decryption chips and their program incompatible. The same modification also served to prevent a bad guy from simply pre-encrypting an entire dictionary and storing it. UNIX Salt What was the modification made by Morris and Thompson? They added a bit of salt. Just as table salt adds zest to grits, the salt that Morris and Thompson sprinkled into the DES algorithm added a little more spice and variety. The DES salt is a 12-bit number, between 0 and 4095, which slightly changes the results of the DES function. Each of the 4096 different salts makes a password encrypt in a different way. When you change your password, the /bin/passwd program selects a salt based on the time of day. The salt is converted into a two-character string and is stored in the /etc/shadow file along with the encrypted password. In this manner when you type your password at login time, the same salt is used again. UNIX stores the salt as the first two characters of the encrypted password. Let’s consider the following entries from the /etc/shadow file on my Solaris system: sam:cdUIOkjWJxzA2:15012:::::: sally:1lJCoa/mnLkA6:15012:::::: alice:ZfbUsVQmAKDCM:15012:::::: bob:v7RcCe3X4sNHo:15012:::::: Do they have the same password? What is/are their passwords? In recent years the security provided by the salt has diminished significantly. Having a salt means that the same password can be encrypted in 4096 different ways. This makes it much harder for an attacker to build a reverse dictionary for translated encrypted passwords back into their encrypted form. To build a reverse dictionary of 100,000 words, an attacker would need to have 409,600,000 entries. But with 8-character passwords and 13-character encrypted passwords, 409,600,000 entries fit in roughly 8 GBs of storage. Another problem with the salt was an error in implementation: many systems selected which salt to use based on the time of day which made some salts more likely than others. crypt(), DES Extended, Modular Crypt Format Several UNIX systems have improved the security of the crypt() function by changing the underlying encryption algorithm. Instead of a modified DES algorithm, a variety of other algorithms have been adopted, including Blowfish and MD5. The advantage of these new algorithms is that more characters of the password are significant, and there are many more possible values for the salt. Both of these changes significantly improve the strength of the underlying encrypted password system. The disadvantage is that the encrypted passwords on these systems will not be compatible with the encrypted passwords on other systems. The Modular Crypt Format (MCF) specifies an extensible scheme for formatting encrypted passwords. MCF is one of the most popular formats for encrypted passwords around today. For example student:$1$mVR1ETu7$/J9SnIZIenedarqK7g1hH/:14491:0:99999:7::: Dollar signs ($) are used to delimit the MCF fields where Field Purpose Notes 1 Specifies encryption algorithm 1 specifies MD5 2 specifies Blowfish 2 Salt Limited to 16 characters 3 Encrypted password Does not include salt, unlike traditional UNIX crypt() function Below are the same four users and their password(s) on a different UNIX system sam:$1$Qw8/Nxz3$x5Elrx6Ho6Iu9P5Vc2StV0:15012:0:99999:7::: sally:$1$IbLyt4w7$d6QaGLihoRLoOh43UG/vZ0:15012:0:99999:7::: alice:$1$B8RsSahC$62PxTDafefARmLa0n5r51/:15012:0:99999:7::: bob:$1$pDSBD3F2$Ub3SY.b7B7WhiwvOakMnX.:15012:0:99999:7::: Do they have the same password? What is/are their passwords? Protecting Passwords As the name implies, a shadow password file is a secondary password file that shadows the primary password file. On Solaris the shadow password file is stored in the file /etc/shadow and contains the encrypted password and a password expiration date. The /etc/shadow file is protected so that it can be read only by the superuser. Thus, an attacker cannot obtain a copy to use in verifying guesses of passwords. Protecting the System Although changes to the encrypted password system have improved the security of encrypted passwords, they have failed to fundamentally address the weakness exploited by password crackers. People pick passwords that are easy to guess! If an attacker can obtain a copy of the password file, it is a simple matter to guess passwords: perform the encryption transform and compare against the shadow file. The best way to deal with the problem of poorly-chosen passwords is to eliminate reusable passwords entirely by using one-time passwords, some form of biometrics, or a token-based authentication system. Such systems can be awkward or expensive. .
Load more

Recommended publications
  • Passwords, Hashes, and Cracks, Oh My! How Mac OS X Implements Password Authentication Dave Dribin “Why Should I Care?”
    Passwords, Hashes, and Cracks, Oh My! How Mac OS X Implements Password Authentication Dave Dribin “Why Should I Care?” • Application Developer • System Administrator • End User Authentication • Authentication is the process of attempting to verify a user’s identity • Passwords authenticate using a “shared secret” History • Mac OS X based on NeXTSTEP • NeXTSTEP Unix on top of Mach • Unix developed by AT&T Bell Labs on DEC PDP-11 • Unix based on mainframe time-sharing systems UNIX Time-Sharing System Version 1 • Released in 1971 • First release of Unix as we know it • Plaintext passwords Plaintext Problems “Perhaps the most memorable [example] occurred in the early 60’s when a system administrator on the CTSS system at MIT was editing the password file and another system administrator was editing the daily message that is printed on everyone’s terminal on login. Due to a software design error, the temporary editor files of the two users were interchanged and thus, for a time, the password file was printed on every terminal when it was logged in.” -- Robert Morris and Ken Thompson, April 3,1978 Unix Versions 3, 4, 5, 6 • Released 1973 through 1975 • Encrypted Password • Password file is readable by all NAME passwd -- password file DESCRIPTION passwd contains for each user the following in- formation: name (login name, contains no upper case) encrypted password numerical user ID GCOS job number and box number initial working directory program to use as Shell This is an ASCII file. Each field within each user's entry is separated from the next by a colon.
    [Show full text]
  • CMSC 426/626 - Computer Security Fall 2014
    Authentication and Passwords CMSC 426/626 - Computer Security Fall 2014 Outline • Types of authentication • Vulnerabilities of password authentication • Linux password authentication • Windows Password authentication • Cracking techniques Goals of Authentication • Identification - provide a claimed identity to the system. • Verification - establish validity of the provided identity. We’re not talking about message authentication, e.g. the use of digital signatures. Means of Authentication • Something you know, e.g. password • Something you have, e.g. USB dongle or Common Access Card (CAC) • Something you are, e.g. fingerprint • Something you do, e.g. hand writing Password-Based Authentication • User provides identity and password; system verifies that the password is correct for the given identity. • Identity determines access and privileges. • Identity can be used for Discretionary Access Control, e.g. to give another user access to a file. Password Hashing Password • System stores hash of the user password, not the plain text password. Hash Algorithm • Commonly used technique, e.g. UNIX password hashing. Password Hash Password Vulnerabilities Assume the authentication system stores hashed passwords. There are eight attack strategies. • Off-line Dictionary Attack - get hold of the password file, test a collection (dictionary) of possible passwords. ‣ Most systems protect the password file, but attackers sometimes get hold of one. • Specific Account Attack - given a specific user account, try popular passwords. ‣ Most systems use lockout mechanisms to make these attacks difficult. • Popular Password Attack - given a popular password, try it on multiple accounts. ‣ Harder to defend against - have to look for patterns in failed access attempts. • Targeted Password Guessing - use what you know about a user to intelligently guess their password.
    [Show full text]
  • Cryptography As an Operating System Service: a Case Study
    Cryptography As An Operating System Service: A Case Study ANGELOS D. KEROMYTIS Columbia University JASON L. WRIGHT and THEO DE RAADT OpenBSD Project and MATTHEW BURNSIDE Columbia University Cryptographic transformations are a fundamental building block in many security applications and protocols. To improve performance, several vendors market hardware accelerator cards. However, until now no operating system provided a mechanism that allowed both uniform and efficient use of this new type of resource. We present the OpenBSD Cryptographic Framework (OCF), a service virtualization layer im- plemented inside the operating system kernel, that provides uniform access to accelerator function- ality by hiding card-specific details behind a carefully designed API. We evaluate the impact of the OCF in a variety of benchmarks, measuring overall system performance, application throughput and latency, and aggregate throughput when multiple applications make use of it. We conclude that the OCF is extremely efficient in utilizing cryptographic accelerator func- tionality, attaining 95% of the theoretical peak device performance and over 800 Mbps aggregate throughput using 3DES. We believe that this validates our decision to opt for ease of use by applica- tions and kernel components through a uniform API and for seamless support for new accelerators. We are grateful to Global Technologies Group, Inc. for providing us with two XL-Crypt (Hifn 7811) boards, one Hifn 6500 reference board, and one Hifn 7814 reference board. We are also grateful to Network Security Technologies, Inc. for providing us with two Hifn 7751 boards, one Broadcom 5820 board, and two Broadcom 5805 boards. In addition, Network Security Technologies funded part of the original development of the device-support software.
    [Show full text]
  • Permissions and Ownership
    Getting Started with Linux: Novell’s Guide to CompTIA’s Linux+ Objective 1 Understand User and Group Configuration Files Information on users and groups on a Linux system is kept in the following files: ■ /etc/passwd ■ /etc/shadow ■ /etc/group Whenever possible, you should not modify these files with an editor. Instead, use the Security and Users modules in YaST or the command line tools described in the next objective, “Manage User Accounts and Groups from the Command Line” on 7-12. Modifying these files with an editor can lead to errors (especially in /etc/shadow), such as a user—including the user root—no longer being able to log in. To ensure consistency of these files, you need to understand how to ■ Check /etc/passwd and /etc/shadow ■ Convert Passwords to and from Shadow /etc/passwd The file /etc/passwd stores information for each user. In the past, UNIX and Linux users were handled in a single file: /etc/passwd. The user name, the UID, the home directory, the standard shell, and the encrypted password were all stored in this file. The password was encrypted using the function crypt (man 3 crypt). In principle, the plain text password could not be deciphered from the encrypted password. 7-2 Version 2 Use the Command Line Interface to Administer the System However, there are programs (such as john) that use dictionaries to encrypt various passwords with crypt, and then compare the results with the entries in the file /etc/passwd. With the calculation power of modern computers, simple passwords can be “guessed” within minutes.
    [Show full text]
  • UNIX Security
    UNIX Security CSE497b - Spring 2007 Introduction Computer and Network Security Professor Jaeger www.cse.psu.edu/~tjaeger/cse497b-s07/ CSE497b Introduction to Computer and Network Security - Spring 2007 - Professor Jaeger UNIX System • Originated in the late 60’s, early 70’s – Bell Labs: Ken Thompson, Dennis Ritchie, Douglas McIlroy • Multiuser Operating System – Enables protection from other users – Enables protection of system services from users • Simpler, faster approach than Multics CSE497b Introduction to Computer and Network Security - Spring 2007 - Professor Jaeger Page 2 UNIX Security • Each user owns a set of files – Simple way to express who else can access – All user processes run as that user • The system owns a set of files – Root user is defined for system principal – Root can access anything • Users can invoke system services – Need to switch to root user (setuid) • Q: Does UNIX enable configuration of “secure” systems? CSE497b Introduction to Computer and Network Security - Spring 2007 - Professor Jaeger Page 3 UNIX Challenges • More about protection than security – Implicitly assumes non-malicious user and trusted system processes • Discretionary Access Control (DAC) – User or their processes may update permission assignments • Each program has all user’s rights • Must trust their processes to be non-malicious • File permission assignments – Assignment based on what is necessary for things to work • All your processes have all your rights • System services have full access – Users invoke setuid (root) procs that have all
    [Show full text]
  • Attachment 2 Crack "Crack Version 4.1" a Sensible Password Checker
    -1- Attachment 2 Crack "Crack Version 4.1" A Sensible Password Checker for Unix Alec D.E. Muffett Unix Software Engineer Aberystwyth, Wales, UK ([email protected] or [email protected]) ABSTRACT Crack is a freely available program designed to find standard Unix eight-character DES encrypted passwords by standard guessing tech- niques outlined below. It is written to be flexi- ble, configurable and fast, and to be able to make use of several networked hosts via the Berkeley rsh program (or similar), where possible. 1. Statement of Intent This package is meant as a proving device to aid the con- struction of secure computer systems. Users of Crack are advised that they may get severly hassled by authoritarian type sysadmin dudes if they run Crack without proper author- isation. 2. Introduction to Version 4.0 Crack is now into it's fourth version, and has been reworked extensively to provide extra functionality, and the purpose of this release is to consolidate as much of this new func- tionality into as small a package as possible. To this end, Crack may appear to be less configurable: it has been writ- ten on the assumption that you run a fairly modern Unix, one with BSD functionality, and then patched in order to run on other systems. This, surprisingly enough, has led to neater code, and has made possible the introduction of greater flexibility which supercedes many of the options that could be configured in earlier versions of Crack. In the same vein, some of the older options are now mandatory.
    [Show full text]
  • A Cryptographic File System for Unix
    ACryptographic File System for Unix Matt Blaze AT&T Bell Laboratories 101 Crawfords Corner Road, Room 4G-634 Holmdel, NJ 07733 [email protected] Abstract algorithms (such as the Data Encryption Standard (DES)[5] and Although cryptographic techniques areplaying an increas- the more recent IDEA cipher[4]) are widely believed sufficiently ingly important role in modern computing system security,user- strong to render encrypted data unavailable to virtually any level tools for encrypting file data arecumbersome and suffer adversary who cannot supply the correct key.However,routine from a number of inherent vulnerabilities. The Cryptographic use of these algorithms to protect file data is uncommon in cur- File System (CFS) pushes encryption services into the file system rent systems. This is partly because file encryption tools, to the itself. CFS supports securestorage at the system level through a extent they are available at all, are often poorly integrated, diffi- standardUnix file system interface to encrypted files. Users cult to use, and vulnerable to non-cryptoanalytic system level associate a cryptographic key with the directories they wish to attacks. Webelieve that file encryption is better handled by the protect. Files in these directories (as well as their pathname file system itself. This paper investigates the implications of components) aretransparently encrypted and decrypted with the cryptographic protection as a basic feature of the file system specified key without further user intervention; cleartext is never interface. stored on a disk or sent to a remote file server.CFS can use any available file system for its underlying storage without modifica- 1.1.
    [Show full text]
  • A Brief History of Cryptography
    University of Tennessee, Knoxville TRACE: Tennessee Research and Creative Exchange Supervised Undergraduate Student Research Chancellor’s Honors Program Projects and Creative Work Spring 5-2000 A Brief History of Cryptography William August Kotas University of Tennessee - Knoxville Follow this and additional works at: https://trace.tennessee.edu/utk_chanhonoproj Recommended Citation Kotas, William August, "A Brief History of Cryptography" (2000). Chancellor’s Honors Program Projects. https://trace.tennessee.edu/utk_chanhonoproj/398 This is brought to you for free and open access by the Supervised Undergraduate Student Research and Creative Work at TRACE: Tennessee Research and Creative Exchange. It has been accepted for inclusion in Chancellor’s Honors Program Projects by an authorized administrator of TRACE: Tennessee Research and Creative Exchange. For more information, please contact [email protected]. Appendix D- UNIVERSITY HONORS PROGRAM SENIOR PROJECT - APPROVAL Name: __ l1~Ui~-~-- A~5-~~± ---l(cl~-~ ---------------------- ColI e g e: _l~.:i~_~__ ~.:--...!j:.~~~ __ 0 epa r t men t: _ {~~.f_':.~::__ ~,:::..!._~_~_s,_ Fa c u 1ty Me n tor: ____Q-' _·__ ~~~~s..0_~_L __ D_~_ ~_o_~t _______________ _ PRO JE CT TITL E: ____~ __ ~c ~ :.f __ l1L~_ ~_I_x __ 9_( __( ~~- ~.t~~-.r--~~ - I have reviewed this completed senior honors thesis "\lith this student and certifv that it is a project commensurate with honors level undergraduate research in this field. Signed ~u:t2~--------------- , Facultv .'vfentor Date: --d~I-~--Q-------- Comments (Optional): A BRIEF HISTORY OF CRYPTOGRAPHY Prepared by William A. Kotas For Honors Students at the University of Tennessee May 5, 2000 ABSTRACT This paper presents an abbreviated history of cryptography.
    [Show full text]
  • UNIX Crypt ( ) Function Takes the User's Password As the Encryption Key and Uses It to Encrypt a 64-Bit Block of Zeros
    8.6 The UNIX Encrypted Password System When UNIX requests your password, it needs some way of determining that the password you type is the correct one. Many early computer systems (and quite a few still around today!) kept the passwords for all of their accounts plainly visible in a so-called "password file" that really contained the passwords. Under normal circumstances, the system protected the passwords so that they could be accessed only by privileged users and operating system utilities. But through accident, programming error, or deliberate act, the contents of the password file almost invariably become available to unprivileged users. This scenario is illustrated in the following remembrance: Perhaps the most memorable such occasion occurred in the early 1960s when a system administrator on the CTSSsystem at MIT was editing the password file and another system administrator was editing the daily message that is printed on everyone's terminal on login. Due to a software design error, the temporary editor files of the two users were interchanged and thus, for a time, the password file was printed on every terminal when it was logged in. - Robert Morris and Ken Thompson, Password Security: A Case History The real danger posed by such systems, wrote Morris and Thompson, is not that software problems will cause a recurrence of this event, but that people can make copies of the password file and purloin them without the knowledge of the system administrator. For example, if the password file is saved on backup tapes, then those backups must be kept in a physically secure place.
    [Show full text]
  • Breaking UNIX Crypt() on the Playstation 3
    Breaking UNIX crypt() on the PlayStation 3 Marc Bevand [email protected] [email protected] Plan DES-based UNIX crypt() password hashes Bitslice DES PlayStation 3©s Cell B.E. processor DES S-Boxes optimized for the Cell Results in numbers: perf/$, perf/W Isn©t UNIX crypt() 30+ years old ? WTF ? DES-based UNIX crypt() Frequently used in large, legacy UNIX environments Still the default in Solaris 10 as well as latest Nevada builds (see CRYPT_DEFAULT in /etc/security/policy.conf) Even in 2008, there is value in optimizing the bruteforcing of UNIX crypt() password hashes Quick reminder UNIX crypt() algorithm: Build a 56-bit key from the passwd Pick a random 12-bit salt to perturb the E box of the DES algorithm DES-encrypt 25 times an all-bits-zero block Passwords limited to 8 chars Salt makes pre-computed attacks 4096 times costlier Best bruteforcing tool (so far) Bitslice DES implemented by Dr Eli Biham in 1997 Represents the most computing intensive part of DES (S- Boxes) as series of logical instructions on 1-bit values On N-bit processors, a bitslice implementation performs N encryptions/decryptions in parallel Implemented in John the Ripper (S-Boxes from Matthew Kwan): 8.8 Mpw/s on quad-core Q6700 @ 2.66 Ghz (2.2 Mpw/s/core, ºonly one saltº) Bitslice DES One S-box maps a 6-bit input to a 4-bit output 8 S-boxes total: S1..S8 Each S-box can be represented by a logical circuit using gates such as AND, OR, XOR, etc Find the circuits with the smallest number of gates No good algorithm is known to find the best circuits, bruteforcing is the only solution Bitslice DES on the Cell B.E.
    [Show full text]
  • A Research UNIX Reader: Annotated Excerpts from the Programmer's
    AResearch UNIX Reader: Annotated Excerpts from the Programmer’sManual, 1971-1986 M. Douglas McIlroy ABSTRACT Selected pages from the nine research editions of the UNIX®Pro grammer’sManual illustrate the development of the system. Accompanying commentary recounts some of the needs, events, and individual contributions that shaped this evolution. 1. Introduction Since it beganatthe Computing Science Research Center of AT&T Bell Laboratories in 1969, the UNIX system has exploded in coverage, in geographic distribution and, alas, in bulk. It has brought great honor to the primary contributors, Ken Thompson and Dennis Ritchie, and has reflected respect upon many others who have built on their foundation. The story of howthe system came to be and howitgrewand prospered has been told manytimes, often embroidered almost into myth. Still, aficionados seem neverto tire of hearing about howthings were in that special circle where the system first flourished. This collection of excerpts from the nine editions of the research UNIX Programmer’sManual has been chosen to illustrate trends and some of the lively give-and-take—or at least the tangible results thereof—that shaped the system. It is a domestic study,aimed only at capturing the way things were in the system’soriginal home. To look further afield would require a tome, not a report, and possibly a more dis- passionate scholar,not an intimate participant. The rawreadings are supplemented by my own recollec- tions as corrected by the memories of colleagues. The collection emphasizes development up to the Seventh Edition (v7*) in 1979, providing only occasional peeks ahead to v8 and v9.
    [Show full text]
  • A Methodology for the Cryptanalysis of Classical Ciphers with Search
    phers with Search Metaheuristics George Lasry A Methodology for the Cryptanalysis of A Methodology for the Cryptanalysis of Classical Ci Classical Ciphers with Search Metaheuristics ISBN 978-3-7376-0458-1 kassel university 9 783737 604581 George Lasry press kassel kassel university press !"# $ % !&' (&)) )*) # + ,)&) - .# +,)/ & + 0123405 / ! & ' & ' & ' 6 # 7 + ))) 8)+$ 9"#)9& )3405 7/':5;.<.5<51.4=>;.0(* 7/':5;.<.5<51.4=>:.;(.* &27++ ?)! ) 04)0:300 $",:5;<5<514=>:; "@'++ . #) +++4443.=4=>:3 '340;9 # !B9$ ) ). ) ,! “After climbing a great hill, one only finds that there are many more hills to climb.” Nelson Mandela Abstract Cryptography, the art and science of creating secret codes, and cryptanalysis, the art and science of breaking secret codes, underwent a similar and parallel course during history. Both fields evolved from manual encryption methods and manual codebreaking techniques, to cipher ma- chines and codebreaking machines in the first half of the 20th century, and finally to computer- based encryption and cryptanalysis from the second half of the 20th century. However, despite the advent of modern computing technology, some of the more challenging classical cipher systems and machines have not yet been successfully cryptanalyzed. For others, cryptanalytic methods exist, but only for special and advantageous cases, such as when large amounts of ciphertext are available. Starting from the 1990s, local search metaheuristics such as hill climbing, genetic algorithms, and simulated annealing have been employed, and in some cases, successfully, for the cryptanal- ysis of several classical ciphers. In most cases, however, results were mixed, and the application of such methods rather limited in their scope and performance. In this work, a robust framework and methodology for the cryptanalysis of classical ciphers using local search metaheuristics, mainly hill climbing and simulated annealing, is described.
    [Show full text]