When you say public-private key pair, you imply that you are talking about asymmetric cryptography. Key sizes here are normally much much bigger than this - 512 bit or 1024 bit are common. If you are actually talking symmetric cryptography, then just randomly generate a 64 bit number (and, if you are using an algorithm like DES/3DES, check it against known weak keys for the algorithm).
– mdma May 24 '10 at 15:52 No. Why can't you store 512 bits on a mobile? Your average text message is far longer than this... If you are new to cryptography, suggest you find a library that does it for you rather than try to learn it for your project.
– David M May 24 '10 at 15:52 it is so because in the application a situation may occur,though it would be very rare, in which the user might have to save the public keys of others manually – sourabh0612 May 24 '10 at 15:56 Let's get this straight.512 bits = 64 bytes. My name, two phone numbers and email address = 58 bytes. Where is the problem with storing 512 bits?
I just don't see it. – David M May 24 '10 at 16:03.
Offhand, I can't think of a public-key cryptography algorithm that would be even somewhat secure with only a 64-bit key. RSA is by far the most common, but for it a 512 bit key is on the small side. Elliptical curve cryptography doesn't require as large of keys as most other public-key algorithms, but even so you typically need somewhere in the range of 150-200 bits.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.