LT   EN   RU  
2021 г. январь 27 д., среда Straipsniai.lt - Информационный портал
  
  Компьютеры > Компьютерные технологии > Безопасность > Криптография
Lankomumo reitingas Версия для печати Версия для печати
Strength of Cryptographic Algorithms

Good cryptographic systems should always be designed so that they are as difficult to break as possible. It is possible to build systems that cannot be broken in practice (though this cannot usually be proved). This does not significantly increase system implementation effort; however, some care and expertise is required. There is no excuse for a system designer to leave the system breakable. Any mechanisms that can be used to circumvent security must be made explicit, documented, and brought into the attention of the end users.

In theory, any cryptographic method with a key can be broken by trying all possible keys in sequence. If using brute force to try all keys is the only option, the required computing power increases exponentially with the length of the key. A 32-bit key takes 232 (about 109) steps. This is something anyone can do on his/her home computer. A system with 56-bit keys, such as DES, requires a substantial effort, but using massive distributed systems requires only hours of computing. In 1999, a brute-force search using a specially designed supercomputer and a worldwide network of nearly 100,000 PCs on the Internet, found a DES key in 22 hours and 15 minutes. It is currently believed that keys with at least 128 bits (as in AES, for example) will be sufficient against brute-force attacks into the foreseeable future.

However, key length is not the only relevant issue. Many ciphers can be broken without trying all possible keys. In general, it is very difficult to design ciphers that could not be broken more effectively using other methods.

Unpublished or secret algorithms should generally be regarded with suspicion. Quite often the designer is not sure of the security of the algorithm, or its security depends on the secrecy of the algorithm. Generally, no algorithm that depends on the secrecy of the algorithm is secure. For professionals, it is easy to disassemble and reverse-engineer the algorithm. Experience has shown that the vast majority of secret algorithms that have become public knowledge later have been pitifully weak in reality.

The keys used in public-key algorithms are usually much longer than those used in symmetric algorithms. This is caused by the extra structure that is available to the cryptanalyst. There the problem is not that of guessing the right key, but deriving the matching private key from the public key. In the case of RSA, this could be done by factoring a large integer that has two large prime factors. In the case of some other cryptosystems, it is equivalent to computing the discrete logarithm modulo a large integer (which is believed to be roughly comparable to factoring when the moduli is a large prime number). There are public-key cryptosystems based on yet other problems.

To give some idea of the complexity for the RSA cryptosystem, a 256-bit modulus is easily factored at home, and 512-bit keys can be broken by university research groups within a few months. Keys with 768 bits are probably not secure in the long term. Keys with 1024 bits and more should be safe for now unless major cryptographical advances are made against RSA. RSA Security claims that 1024-bit keys are equivalent in strength to 80-bit symmetric keys and recommends their usage until 2010. 2048-bit RSA keys are claimed to be equivalent to 112-bit symmetric keys and can be used at least up to 2030.

It should be emphasized that the strength of a cryptographic system is usually equal to its weakest link. No aspect of the system design should be overlooked, from the choice of algorithms to the key distribution and usage policies.

            

Lankomumo reitingas

Oбсудить на форуме - Oбсудить на форуме

Версия для печати - Версия для печати

Назад
Случайные теги:    Архитектура (3)    Любовь (32)    Ислам (3)    Страны (22)    Здоровье (86)    Йога (9)    Сельское хозяйство (19)    Фехтирования (6)    Фильмы (10)    Культура (88)    Генетика (10)    Туризм (25)    Компьютеры (290)    Технологий (4)    Собаки (6)    Буддизм (3)    Кормление грудью (5)    Филателия (15)    Медицина (84)    Набоков В. В. (94)    Английский язык (2)    Настольные игры (17)    Анна Ахматова (3)    Лов рыбы (11)    Открытый код (2)    Хакеры (116)    Садоводство (12)    Египет (5)    Литература (4)    Книги (2)    Саентология (10)    Прогр. обеспечение (15)    Общение (322)    НЛП (18)    Боевые искусства (10)    Люди (94)    Пиво (29)    Еврейи (10)    Образование (101)    Автомобили (6)    Драконы (12)    Математика (2)    Политика (3)    Психиатрия (13)    Хоби (27)    Физкультура (3)    Процессоры (7)    Мама и ребенок (19)    Астрономия (10)    Кормление (4)
1. Криптография: зачем это нужно
2. Криптография с открытым ключом: от теории к стандарту
3. Алгоритм шифрования данных с открытым ключом RSA
4. Будем шифроваться? или Практикум по домашней криптографии
5. Часто задаваемые вопросы и ответы по парольной защите документов Microsoft Office (FAQ)
6. Надежна ли цифоровая подпись?
7. IBM Выпустил новый алгоритм Signcryption
8. Анализ рынка средств защиты программного обеспечения от несанкционированного копирования. Часть I. StarForce.
9. Как обеспечить подлинность электронных документов?
10. Анализ рынка средств защиты программного обеспечения от несанкционированного копирования. Часть 2. StarForce
1. Часто задаваемые вопросы и ответы по парольной защите документов Microsoft Office (FAQ)
2. Курс по криптоанализу блочный шифров Брюса Шнаера
3. Криптография: зачем это нужно
4. Криптография с открытым ключом: от теории к стандарту
5. Практическая криптография: алгоритмы и их программирование
6. Алгоритм шифрования данных с открытым ключом RSA
7. Будем шифроваться? или Практикум по домашней криптографии
8. Надежна ли цифоровая подпись?
9. Как обеспечить подлинность электронных документов?
10. Анализ рынка средств защиты программного обеспечения от несанкционированного копирования. Часть I. StarForce.
Map