Critiques of measurements for the cryptography
-
Hello dear reader. I want to know about critique of measurements for cryptography if it has. I did symmetric key encryption and decryption algorithms ready but could not check that encryption and decryption algorithms are satisfied to the real good cryptography or not. Please help me to make sure the algorithms. If someone knows about this prob or to know the person, who are good at the cryptography, please leave me message or contact with me by byambaak@yahoo.com. I really wanna check my encryption decryption algorithms. Thank you.
-
Hello dear reader. I want to know about critique of measurements for cryptography if it has. I did symmetric key encryption and decryption algorithms ready but could not check that encryption and decryption algorithms are satisfied to the real good cryptography or not. Please help me to make sure the algorithms. If someone knows about this prob or to know the person, who are good at the cryptography, please leave me message or contact with me by byambaak@yahoo.com. I really wanna check my encryption decryption algorithms. Thank you.
The first step is to verify random-ness. You can do this by simply analyzing the output. If the output of any cipher is not near random results for decent amount of text then there is a good chance you are leaking bits. Leaking bits is a term to say that a bit comes through with minimal operatons performed on it and can lead you to the answer by reducng the possibilities. The next step should be to verify the key is not inferred directly by result. encrypt a text file or large text using one key, and another which is only ONE byte dfference (preferably one bit also). For instance keys: TexasHoldem1 and TexasHoldem2. the two files should have no overlapping characters. If any characters are the same in the same position, it may be chance, but you will want to test again with TexasHoldem3 and TexasHoldem4. If that same byte is not changing, or the byte is changing less oftan than others, again this is an obvious sign you are leaking bits. Then find a mathematician to help with the final assessment.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
The first step is to verify random-ness. You can do this by simply analyzing the output. If the output of any cipher is not near random results for decent amount of text then there is a good chance you are leaking bits. Leaking bits is a term to say that a bit comes through with minimal operatons performed on it and can lead you to the answer by reducng the possibilities. The next step should be to verify the key is not inferred directly by result. encrypt a text file or large text using one key, and another which is only ONE byte dfference (preferably one bit also). For instance keys: TexasHoldem1 and TexasHoldem2. the two files should have no overlapping characters. If any characters are the same in the same position, it may be chance, but you will want to test again with TexasHoldem3 and TexasHoldem4. If that same byte is not changing, or the byte is changing less oftan than others, again this is an obvious sign you are leaking bits. Then find a mathematician to help with the final assessment.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Thanks for your answering. That three critiques can satisfy for any cryptography? If my encryption input is focused on the small numbers as a number inside 1000 then above critiques can satisfy mine? If no,what should i do better to keep my input as security? I can change and expand my input until as much as i wanted and encrypt it but problem is that simple brute force attack can find my input number easily without find my encrypting. Is this any method to keep security if input is small. I have necessary to encrypt my input and send it through the network what should i do this time? I have though about that much but have no more good idea to decide the prob. Please help me? Thank you
-
Thanks for your answering. That three critiques can satisfy for any cryptography? If my encryption input is focused on the small numbers as a number inside 1000 then above critiques can satisfy mine? If no,what should i do better to keep my input as security? I can change and expand my input until as much as i wanted and encrypt it but problem is that simple brute force attack can find my input number easily without find my encrypting. Is this any method to keep security if input is small. I have necessary to encrypt my input and send it through the network what should i do this time? I have though about that much but have no more good idea to decide the prob. Please help me? Thank you
Bimbaa wrote:
That three critiques can satisfy for any cryptography?
No, those are the first steps you must do before you pull in the big guns of a mathematician and not waste his time. If you haven't done the initial work, he isn't going to be very happy with you. As to brute force, you are not worried about brute force, per se. True if your algorithm is so fast that it makes brute force easier that is a problem, but then there are always longer keys. The main thing you are concerned about is leaked key content into the message. One reason we use Triple DES is that DES leaks bits. Re-encrypting it 3 times attempts to hide those bits again. DES was cracked using a non-brute force attack because of a fault in the algorithm. I have developed several algorithms over the years that satisfied the initial tests, but still failed on the full analysis. One got away and was used for nefarious purposes, luckily for everyone it had a flaw. I have since retired from most cryptography except as entertainment. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Bimbaa wrote:
That three critiques can satisfy for any cryptography?
No, those are the first steps you must do before you pull in the big guns of a mathematician and not waste his time. If you haven't done the initial work, he isn't going to be very happy with you. As to brute force, you are not worried about brute force, per se. True if your algorithm is so fast that it makes brute force easier that is a problem, but then there are always longer keys. The main thing you are concerned about is leaked key content into the message. One reason we use Triple DES is that DES leaks bits. Re-encrypting it 3 times attempts to hide those bits again. DES was cracked using a non-brute force attack because of a fault in the algorithm. I have developed several algorithms over the years that satisfied the initial tests, but still failed on the full analysis. One got away and was used for nefarious purposes, luckily for everyone it had a flaw. I have since retired from most cryptography except as entertainment. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
