Good idea!
You're right that I can use it in your way - the combination of symmetric
keys. But remember, if the symmetric key is fast to generate and the code
fast to decrypt - they can decode easily your message using appropriate
attack. The high cost of the asymmetric keys brings you more security,
that's why I am trying to use it in this way.
Bye, Jakub!


Haytham Mohammed wrote:
> 
> Hi jakub
>    
>   I think u want to send an message to multiple of receivers using
> asymmetric algorithm
>    
>   Note that most public key algorithms are relatively computationally
> costly (relatively slow), in comparison with many symmetric key
> algorithms.
>    
>   hybrid cryptosystems (public key algorithms and symmetric key
> algorithms) for reasons of efficiency are used; 
>    
>   1- in such a cryptosystem, a shared secret key ("session key") is
> generated by one party, this session key is then encrypted by each
> recipient's public key. 
>    
>   2-  Each recipient uses the corresponding private key to decrypt the
> session key. 
>    
>   Once all parties have obtained the session key, 
>    
>   3- they can use a much faster symmetric algorithm to encrypt and decrypt
> messages.
>    
>   Reference:
>   http://en.wikipedia.org/wiki/Public-key_cryptography
>    
>   Regards 
>   Haytham
> 
> 
> Jakub <[EMAIL PROTECTED]> wrote:
>   
> Please could somebody tell me, how do I substitute 2 different public
> keys?
> Or, better, encrypt one message for 2 receivers at a time (or using the
> combined key - the same)? (I know that i.e. RSA allows it)
> Bye Jakub
> 
> -- 
> View this message in context:
> http://www.nabble.com/Key-Substitution-tf2192069.html#a6066106
> Sent from the Crypto++ forum at Nabble.com.
> 
> 
> 
>               
> ---------------------------------
> Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+
> countries) for 2ยข/min or less.
> 

-- 
View this message in context: 
http://www.nabble.com/Key-Substitution-tf2192069.html#a6180064
Sent from the Crypto++ forum at Nabble.com.


Reply via email to