Perimeter
2/8/2012
11:10 PM
Taher Elgamal
Taher Elgamal
Commentary
Connect Directly
RSS
E-Mail
50%
50%

How Can We Gracefully Update Crypto?

Cryptographic methods at any point in time will become weak at some point due to the advances made in computing

The recently disclosed weakness in the RSA keys found on the Web makes one rethink the strategy of how to use cryptography on a large scale.

In fact, a cryptographic algorithm can become weak or unacceptable at any point in time. What is also true is that all cryptographic methods used in practice at any point in time will become weak at some point in the future due to the advances made in computing over the years.

Since the early days in modern crypto, we knew that we would have to update the methods we use on a regular basis. Unless we use an extremely large size key -- which is not very practical, obviously -- we would need to update symmetric keys from 128- to 256 to higher values, and similarly for asymmetric keys. The experience we had a few years ago with the discovered MD5 weaknesses did not seem to change the way we look at the use of crypto.

Someday we may be able to gracefully increase key sizes without major disruptions, but what happens if an algorithm is known to be weak as was the case with MD5. Can we perhaps use a backup certificate with a different algorithm that is created at the same time and is used when the primary certificate used a weak algorithm?

Maybe someday.

Recognized in the industry as the "inventor of SSL," Dr. Taher Elgamal led the SSL efforts at Netscape. He also wrote the SSL patent and promoted SSL as the Internet security standard within standard committees and the industry. Dr. Elgamal invented several industry and government standards in data security and digital signatures area, including the DSS government standard for digital signatures. He holds a Ph.D. and M.S. in Computer Science from Stanford University.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-1556
Published: 2014-09-12
Cross-site scripting (XSS) vulnerability in Synology Photo Station 5 for DiskStation Manager (DSM) 3.2-1955 allows remote attackers to inject arbitrary web script or HTML via the name parameter to photo/photo_one.php.

CVE-2014-2008
Published: 2014-09-12
SQL injection vulnerability in confirm.php in the mPAY24 payment module before 1.6 for PrestaShop allows remote attackers to execute arbitrary SQL commands via the TID parameter.

CVE-2014-2009
Published: 2014-09-12
The mPAY24 payment module before 1.6 for PrestaShop allows remote attackers to obtain credentials, the installation path, and other sensitive information via a direct request to api/curllog.log.

CVE-2014-4735
Published: 2014-09-12
Cross-site scripting (XSS) vulnerability in MyWebSQL 3.4 and earlier allows remote attackers to inject arbitrary web script or HTML via the table parameter to index.php.

CVE-2014-5259
Published: 2014-09-12
Cross-site scripting (XSS) vulnerability in cattranslate.php in the CatTranslate JQuery plugin in BlackCat CMS 1.0.3 and earlier allows remote attackers to inject arbitrary web script or HTML via the msg parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
CISO Insider: An Interview with James Christiansen, Vice President, Information Risk Management, Office of the CISO, Accuvant