Security
  Home arrow Security arrow Page 5 - PKI: Looking at the Risks
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBM® developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
VPS Hosting  
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid  
Request Media Kit
Contact Us  
Site Map  
Privacy Policy  
Support  
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
Google.com  
SECURITY

PKI: Looking at the Risks
By: Eliana Stavrou
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 9
    2005-01-24


    Table of Contents:
  • PKI: Looking at the Risks
  • Trust establishment
  • Private key protection
  • CRL availability
  • Key generation
  • Legislation compliance

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article

     
     
    ADVERTISEMENT


    PKI: Looking at the Risks - Key generation
    ( Page 5 of 6 )

    The generation of the public and private key is done using a cryptographic algorithm, and the generation of a digital signature is done using a hash algorithm. Examples of well known cryptographic algorithms are RSA (Rivest - Shamir - Aldeman), Diffie – Hellman, Elliptic Curve and DSS (Digital Signature Standard). Examples of well known hash algorithms are MD2, MD4, MD5 and SHA (Secure Hash Algorithm).

    The risk associated with the cryptographic or hash algorithm used to generate the keys or digital signature respectively, pertains to the length of the keys that define the strength of the algorithm. By using a limited bit length to generate the keys or the digital signature, you face the risk of a brute force attack, in which an intruder tests every possible key combination to break the cryptographic or hash algorithm. These days, a brute force attack is easily made as computers get faster and cheaper.

    Keep in mind that, if an attacker uses brute force, the computing power that is needed to break the algorithm increases exponentially with the length of the key. For example, a 32 bit length key requires 232 combinations; a key of this length can be easily broken even by you using special software. These days, a 512 bit length key can be broken by major governments or university research groups within a few months.   

    In theory, any cryptographic method can be broken by trying all possible combinations. Fortunately, at the moment large length keys (i.e. 2048 bits) are unbreakable. By the time a cryptographic algorithm is broken, usually a new, stronger algorithm appears to cover the loss.  

    How to minimize the risk: There is always the risk of using weak algorithms, which generate the public key from the private key in a manner that allows the value of the private key to be determined. Each issuing authority must use well-known algorithms and a large bit length for the generated keys to prevent an attacker from predicting the keys and causing problems. In addition, anyone requesting a digital certificate should take some time reading the Certificate Practice Statement of the issuing authority; it states the key length and the cryptographic and hash algorithms used. By doing so, all parties could prevent the creation of weak keys that can be determined by an intruder.  



     
     
    >>> More Security Articles          >>> More By Eliana Stavrou
     

       

    SECURITY ARTICLES

    - Critical Microsoft Visual Studio Security Pa...
    - US Faces Tech Security Expert Deficit
    - LAN Reconnaissance
    - An Epilogue to Cryptography
    - A Sequel to Cryptography
    - An Introduction to Cryptography
    - Security Overview
    - Network Security Assessment
    - Firewalls
    - What’s behind the curtain? Part II
    - What’s behind the curtain? Part I
    - Vectors
    - PKI: Looking at the Risks
    - A Quick Look at Cross Site Scripting
    - PKI Architectures: How to Choose One





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 4 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek