Symmetric Key Distribution Protocol with Hybrid Crypto Systems

Symmetric Key Distribution Protocol with Hybrid Crypto Systems Tony Nguyen

Key Distribution Protocol Ø Utilized symmetric and asymmetric algorithm to complement each other weaknesses. Ø Using digital certificate, MD 5 and session key to meet the goal of security in terms of authenticity, integrity and confidentiality. 07/29/2009 Hybrid Crypto Systems CS 691 Page 1/15

Symmetric Encryption Ø One key for encryption and decryption. Ø Faster than asymmetric cryptography. Ø Some algorithms: DES, 3 DES, Blowfish, AES. Ø Key length: 64 -256 bits

Asymmetric Encryption Ø Ø Public key for encryption and private key for decryption. Key management is easier than symmetric. Some algorithms: RSA and El. Gammal Key length: At least 3072 bits to be secure.

Digital Certificate Ø Verify that the public key belongs to an individual. Ø Generate self-sign certificate using openssl. Ø Request public key certificate sign by trusted authority such as Thawte or Verisign. Ø Digital certificate usually have a time expiration on it.

Hybrid Crypto Protocol – Step 1 Ø Alice is sending its digital certificate to Bob. Ø Bob receives and verifies the certificate with CA’s public key.

Hybrid Crypto Protocol – Step 2 Ø Bob send its digital certificate to Alice. Ø Alice receives Bob’s certificate and verify it with CA.

Hybrid Crypto Protocol – Step 3 Ø Alice encrypting the nonce and unique identifier with Bob’s public key and send it to Bob. Ø Bob decrypt the message from Alice with Bob’s private key and keep the nonce value and verify the unique identifier.

Hybrid Crypto Protocol – Step 4 Ø Bob sends the nonce value which it received from Alice and its own nonce value encrypting it with Alice’s public key. Ø Alice decrypted the message with secret key and verify the nonce value from Bob to assure that the correspond is Bob because only Bob can decrypt this message.

Hybrid Crypto Protocol – Step 5 • Alice sends secret key (session key) with the nonce value from Bob and encrypt this message with Bob’s public key to ensure that Bob is the only one can read the message and to assure Bob that the sender is Alice. • Bob receive the message and decrypt with private key. Compare the incoming nonce that he has originally sent to confirm the correspondent is Alice.

Discussion • Is it possible for an attacker to break in the middle? • What if the attacker has compromised the CA?

Conclusion Ø Securely transmit private key with mutual authentication and trusted third party. Ø Provides confidentiality, authenticity and integrity.

References • http: //en. wikipedia. org/wiki/Key_(cryptograp hy) • http: //www. akadia. com/services/ssh_test_cer tificate. html • http: //portal. acm. org/citation. cfm? id=948737. 948764